Update projects to use GBIF Metadata Profile version 1.1 (currently 1.0.2)

16419
Reporter: kbraak
Assignee: kbraak
Type: Story
Summary: Update projects to use GBIF Metadata Profile version 1.1 (currently 1.0.2)
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2014-09-19 10:22:29.603
Updated: 2014-11-27 08:58:24.426
Resolved: 2014-11-27 08:58:24.401
        
Description: Currently all our projects use GBIF Metadata Profile version 1.0.2

Please note, the GBIF Metadata Profile is still maintained in SVN here: https://code.google.com/p/gbif-metadata/source/browse/#svn%2Ftrunk%2Feml-gbif-profile

A number of changes have been made to the GBIF Metadata Profile already, and more changes are still needed:

-Pending 1: Support multiple Collections
-Pending 2: Move specimenPreservationMethod into CuratorialUnit-
-Pending 3: Support multiple creator/metadataProvider/contact
-Pending 4: Add userId to agent
-Pending 5: Move formationPeriod and livingTimePeriod into Collection-

These schema changes are under review in http://dev.gbif.org/code/cru/CR-GBIFCOM-77

For each change, there may be API, registry, IPT, or Portal changes needed. Please create a sub-task for each of the changes required below:

Pending 1. Support multiple Collections
(API) No change needed. Dataset supports List collections
(IPT) Requires change to form
(Registry) Update EML parsers, and EML template
(Portal) Show as list on Dataset page

-Pending 2. Move specimenPreservationMethod into CuratorialUnit-
*(API) Requires PreservationMethodType moved from Collection, to CuratorialUnit.*
(IPT) Requires change to form
(Registry) Update EML parsers, and EML template
(Portal) Adjust how shown on Dataset page

Pending 3. Support multiple creator/metadataProvider/contact
(API) No change required, Dataset has List contacts
(IPT) Requires change to form
(Registry) Update EML parsers, and EML template
(Portal) Adjust how shown on Dataset page

Pending 4. Add userId to agent
(API) No change required, Contact has List userId
(IPT) Requires change to form
(Registry) Update EML parsers, and EML template
(Portal) Show on Dataset page

-Pending 5. Move formationPeriod and livingTimePeriod into Collection-
*(API) Requires List of VerbatimTimePeriod added to Collection - currently is independent as List of TemporalCoverage on Dataset*
(IPT) Requires change to form
(Registry) Update EML parsers, and EML template
(Portal) Show as part of Collection on Dataset page

1. MaintenanceUpdateFrequency element added to schema.
*(API) Requires new ENUM added to API, field added to Dataset*
(IPT) Requires new form field
(Registry) Update EML parsers, and EML template
(Portal) Show on Dataset page

-2. Abstract element is now unbounded, and can have xml:lang-
*(API) Change needed to capture language of multiple paragraphs*
(IPT) Update form field, to make it possible to enter multiple abstract in several languages.
(Registry) Update EML parsers, and EML template. Ensure lossless round-tripping possible: eml.xml -> Dataset -> eml.xml. Ensure multilingual abstract searchable via registry full text search.
(Portal) Show multiple paragraphs separately on Dataset page? Show multilingual paragraphs on Dataset page?

-3. Keyword element can have xml:lang-
*(API) Change needed to preserve keyword language*
(IPT) Update form field, to make it possible to enter multiple keywords in several languages.
(Registry) Update EML parsers, and EML template. Ensure lossless round-tripping possible: eml.xml -> Dataset -> eml.xml. Ensure multilingual keyword searchable via registry full text search.
(Portal) Show multilingual keywords on Dataset page?

-4. Title element is now unbounded, and can have xml:lang-
*(API) Change needed to preserve multiple titles and their language*
(IPT) Update form field, to make it possible to enter multiple titles in several languages.
(Registry) Update EML parsers, and EML template. Ensure lossless round-tripping possible: eml.xml -> Dataset -> eml.xml. Ensure multilingual title searchable via registry full text search.
(Portal) Show multilingual titles on Dataset page?

-5. Project title element can have xml:lang-
*(API) Change needed to preserve title language*
(IPT) Update form field, to make it possible to enter project title language.
(Registry) Update EML parsers, and EML template. Ensure lossless round-tripping possible: eml.xml -> Dataset -> eml.xml.
(Portal) Show language of project title on Dataset page?

6. Project personnel is now unbounded
(API) No change needed, since Project.contacts List exists already
(IPT) Update form field, to make it possible to enter multiple project personnel.
(Registry) Update EML parsers, and EML template. Ensure lossless round-tripping possible: eml.xml -> Dataset -> eml.xml.
(Portal) Show mutiple project personnel on Dataset page

-7. Project abstract element added, which is unbounded, and can have xml:lang-
*(API) Change needed to preserving paragraph language*
(IPT) Add form field, to make it possible to enter multiple project abstract in several languages.
(Registry) Update EML parsers, and EML template. Ensure lossless round-tripping possible: eml.xml -> Dataset -> eml.xml. Ensure multilingual project abstract searchable via registry full text search.
(Portal) Show multiple project paragraphs separately on Dataset page? Show multilingual project paragraphs on Dataset page?

8. Project funding no longer required
(API) No change needed
(IPT) Make non-mandatory field.
(Registry) No change needed.
(Portal) No change needed

9. Project StudyAreaDescription no longer required
(API) No change needed
(IPT) Make non-mandatory field.
(Registry) No change needed.
(Portal) No change needed

10. Project DesignDescription no longer required
(API) No change needed
(IPT) Make non-mandatory field.
(Registry) No change needed.
(Portal) No change needed

11. Collection ParentCollectionIdentifier no longer required
(API) No change needed
(IPT) Make non-mandatory field.
(Registry) No change needed.
(Portal) No change needed

12. Collection CollectionIdentifier no longer required
(API) No change needed
(IPT) Make non-mandatory field.
(Registry) No change needed.
(Portal) No change needed

-13. Collection name element can have xml:lang-
*(API) Change needed to preserve name language*
(IPT) Update form field, to make it possible to enter collection name language.
(Registry) Update EML parsers, and EML template. Ensure lossless round-tripping possible: eml.xml -> Dataset -> eml.xml.
(Portal) Show language of collection name on Dataset page?]]>
    

Author: kbraak@gbif.org
Created: 2014-11-27 08:58:24.423
Updated: 2014-11-27 08:58:24.423
        
Changes that would have required us to break the API have been postponed until a later date.

The final list of changes required for GBIF Metadata Profile version 1.1 is captured in POR-2562 (API), POR-2560 (registry-metadata), POR-2561 (registry console)

Closing issue.