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

Reset dublincore metadata when a document is copied

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 7.10
    • Fix Version/s: 7.10-HF04, 8.2
    • Component/s: Core
    • Impact type:
      API change
    • Upgrade notes:
      Hide

      From nuxeo 8.2, dc:creator, dc:creationDate, dc:modification and dc:contributors metadata are reseted for documents created from a template.
      This behavior can be enabled for all copy on nuxeo platform by setting the configuration property 'nuxeo.dclistener.reset-creator-on-copy' to true.

      Show
      From nuxeo 8.2, dc:creator, dc:creationDate, dc:modification and dc:contributors metadata are reseted for documents created from a template. This behavior can be enabled for all copy on nuxeo platform by setting the configuration property 'nuxeo.dclistener.reset-creator-on-copy' to true.

      Description

      Currently the copied document keeps the same author, creation date and last modification date as the original document. We should at least reset these metadata with the current user as the new author and the current date as the new creation date and last modification date.

      Metadata dc:creator, dc:creationDate, dc:modification and dc:contributors are now reseted for documents created from a template (workspace template). You can also enable this behaviour fo all kind of document copies by setting nuxeo.dclistner.reset-creator-on-copy configuration property to true.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.