Version Control metadata needed to manage status, version, date of docs

    • Type: Task
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: General
    • None
    • Environment:

      Recommendation for Specification

    • Hide

      Develop recommendation for versioning metadata in Specification.

      Show
      Develop recommendation for versioning metadata in Specification.
    • Hide

      When referencing versioning, there are two areas of versioning to consider; 1) document versioning and 2) content model versioning. The issue raised here pertains to document versioning.
      Document versioning applies to management of documents/content items in the eTMF. Version management is an application- and implementation-specific task. However, Document Versioning is supported with the new core metadata tag, Document Version in the eTMF Standard. The February 17, 2014 TC meeting Powerpoint (PPT) has details of how document/content item versioning is supported through use of a major.minor versioning approach. The major version number indicates a change to a content item; the minor version number indicates a change to the metadata for the content item. There is no specific version management policy specified in the eTMF Charter other than the version number text specifications and examples given in the TC PPT.

      Show
      When referencing versioning, there are two areas of versioning to consider; 1) document versioning and 2) content model versioning. The issue raised here pertains to document versioning. Document versioning applies to management of documents/content items in the eTMF. Version management is an application- and implementation-specific task. However, Document Versioning is supported with the new core metadata tag, Document Version in the eTMF Standard. The February 17, 2014 TC meeting Powerpoint (PPT) has details of how document/content item versioning is supported through use of a major.minor versioning approach. The major version number indicates a change to a content item; the minor version number indicates a change to the metadata for the content item. There is no specific version management policy specified in the eTMF Charter other than the version number text specifications and examples given in the TC PPT.

      "Regarding the question of document and data exchange on just final achiveable records, we need to enable the real-time document exchange for collaboration and oversite. Key metadata must include the status of the document, the version and date of the document. A big waste of time in management of TMFs the discernment if the document is a duplicate to an existing document, the content has changed, the metadata has changed, or if it is an entirely new document and metadata." - Michael Agard
      Found in - http://www.linkedin.com/groups/Global-eTMF-Standards-Telecon-call-5161997.S.5793078168692731904?qid=00861586-c5a0-4c3c-be06-d870a51633fb&trk=groups_items_see_more-0-b-ttl

            Assignee:
            Unassigned
            Reporter:
            Jennifer Alpert Palchak (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: