Details

    • Type: Technical Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 6.2.0 CE M2
    • Fix Version/s: None
    • Component/s: Documents & Media
    • Labels:
      None

      Description

      Currently, global scoped Document Types are not exported to the LAR (see LPS-22788). As a result, you lose files metadata when importing.

      Steps to reproduce:
      1. Go to the Global Documents and Media application in the control panel.
      2. Create a new document type "MyGlobalDocType", add some fields to it
      3. Add a pre-created metadata set to MyGlobalDocType, for instance "Meeting Metadata"
      4. Create a folder "f1", define specific document type restrictions to allow the "MyGlobalDocType" document type
      5. Create a document "doc1" of "myGlobalDoctype" type inside the folder
      6. Create a document "doc2" of pre-created type "Contract" in the root folder
      7. Export the Documents and Media data into a LAR
      8. Import the LAR in the Global Documents and Media application on a new portal instance/liferay installation

      Observed behavior:

      • Imported Documents lose both the association to their document types and the meta-data, even if the document types were pre-created.
      • Imported folder loses the document type restrictions
      • No new document type/metadata sets are created

      Expected behavior:
      a) Non-existent, non-precreated metadata sets should be created (same applies to document types). In the example:
      . A new metadata set for "MyGlobalDocType" is created
      . A new document type "MyGlobalDocType" is created and associated with that metadata set
      b) Existing, non-precreated metadata sets should be updated (same applies to document types). In the example, if step 8 is repeated,
      . The metadata set for "MyGlobalDocType" is updated
      . The "MyGlobalDocType" document type is updated
      c) Pre-created metadata sets should be kept as they are. Instead, a new metadata set must be created (same applies to document types). In the example:
      . The existing metadata set for "Contract" is not modified. A new "Contract (2)" metadata set is created using the incoming uuid
      . The existing metadata set for "Meeting Metadata" is not modified. A new "Meeting metadata (2)" set is created using the incoming uuid
      . The existing "Contract" document type is not modified. A new "Contract (2)" Document type is created using the incoming uuid, and associated with "Contract (2)" metadata set.
      . The "MyGlobalDocumentType" is associated to the new "Meeting Metadata (2)" set.
      . Subsequent imports will update those new elements (see case b)
      d) All imported File Entries and Folders should be linked to the newly created/updated document types. In the example:
      . The imported contract "doc2" should be associated to the "Contract (2)" document type
      . The imported folder "f1" should be restricted to contain "MyGlobalDocType" document type
      . The imported document "doc1" should be associated to the "MyGlobalDocType" document type
      e) All metadata values should be imported and associated to the File Entries.

      This issue needs to be solved prior to dealing with site-scoped references to global Document Types and Metadata Sets.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              support-lep@liferay.com SE Support
              Reporter:
              daniel.sanz Daniel Sanz
              Recent user:
              Mate Thurzo (Inactive)
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                2 years, 29 weeks, 2 days ago

                  Packages

                  Version Package