Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-30767

Compound Docs - Master Epic

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: DAM
    • Team(s):
      PLATFORM

      Description

      It is foundational for PAM use cases to be able to deal with complex documents and the notion of compound assets. We need to be able to handle this “new” type of document for PAM, including complex layouts, 3D and complex video.

      We can define Compound Documents as files that only make sense as a group of interrelated children, possibly at several levels, each of these is modifiable.  

      We need to handle Compound Documents within all the core functionalities possible with the platform; such as upload, preview, versioning, search, share, and approval workflows. 

      PAM will be delivered as a componentized PAM application, Compound Documents will need to work within this context. 

      These are the main categories currently identified: 

      1. Material files: xtex, u3m are the main material format to structure the compound.
      2. Complex Layouts: Page Layouts: native layouts (.indd or .ai), pdf for preview (if needed), n-ancillary files (txt, pdf, json), subfolder with n-linked component files (images, illustrator, pdfs...)
      3. Product Designs: main 3D design file (obj, clo, zproj. lxo, xtex etc.), glb for preview, image for thumb (jpg, png), n-ancillary files (any formats),  subfolder with n-texture files (image formats)

       

      For later: Complex Video: Video Projects: native Premiere project (.proj) or Avid project (.avp, .avs), preview (mp4 or similar), n-ancillary files,  subfolder with n-components (video, audio, images or graphics formats).

       

      Outcome for this iteration:

      Be able to upload compound documents following a defined structure for its type and apply metadata accessible from the parent if metadata also exists at the children level, so that I can easily search my compound document. Compound Documents can also be inside compound documents (ie. Product Design.

      Resources: 
      The shaping doc with scope: PAM - Compounds Shaping Doc.docx
      Ideas of iterations (to develop, modify..): PAM Core Iterations.docx
      Mockups: https://www.figma.com/file/pE2EVqyOecy03y5EIgOaSp/Compound-documents?node-id=146%3A747 
      Test documents: Compound Documents Testing and Compound document testing

      We also have a miro board that helped define the shaping doc.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mlumeau Manon Lumeau
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: