Checklist for Metadata Changes

Changes in Quellcode

 * (JK) update Metadata Schemas in
 * common_logic/src/main/resources/xsd/metadata/0.1/
 * public schemas on http://metadata.mpdl.mpg.de/escidoc/metadata/schemas/0.1/ (location on srv03: /srv/www/metadata/escidoc/metadata/schemas/0.1/)
 * Decision: extend with JusCMS genres/creator roles and new metadata (in schema only, not in PubMan code)


 * update XSLTs in
 * transformation (partly done, the newer transformations + LL, ZFN, other migrations)
 * structured_exportmanager (status has to be checked)
 * cone_presentation (no changes needed)
 * validation (partly done, has to be revised and retested)
 * parent poms (both property sections) (todo)
 * citation styles (status has to be checked)
 * update ValueObjects (will not be done for new genres and new metadata)
 * update JibX-Bindings
 * check eSciDoc Admin and OU metadata changes (
 * if necessary update GUI/JSPFs (needed only if changes in Value objects)
 * if necessary update Resource bundles (needed only if changes in value objects)
 * tests and test.xmls have to be updated (partly done, has to be re-checked)

Changes in Colab

 * update Metadata Profiles
 * --Natasa 12:16, 13 November 2009 (UTC)noticed that languages are encoded from RFC.....
 * we use language list from http://www.loc.gov/standards/iso639-2/langhome.html (which is also in Cone). Application profile should also be changed.


 * update Metadata Sets
 * add also JusCMS specific genres for genre type and source type? (list is available)--Natasa 16:38, 25 November 2009 (UTC)
 * add JusCMS author roles (list is available)?--Natasa 16:38, 25 November 2009 (UTC)
 * update Mapping Specifications

Infrastructure

 * update foxmls (items, contexts)
 * check if update includes the URI values as specified in for e.g. publication types
 * check if all "enumerations" indeed have own URI (see some comments at http://colab.mpdl.mpg.de/mediawiki/ESciDoc_Encoding_Schemes#Content_Category_Encoding_Scheme )
 * update lucene template
 * recache + reindex
 * check search indices

CONE

 * clarify modification of identifiers
 * clarify modification of predicates


 * "http://escidoc.mpg.de/award"
 * "http://escidoc.mpg.de/created-by"
 * "http://escidoc.mpg.de/degree"
 * "http://escidoc.mpg.de/modified-by"
 * "http://escidoc.mpg.de/person-activity-status"
 * "http://escidoc.mpg.de/position"
 * "http://purl.org/dc/elements/1.1/identifier"
 * "http://purl.org/dc/elements/1.1/title"
 * "http://purl.org/dc/terms/alternative"
 * "http://purl.org/dc/terms/created"
 * "http://purl.org/dc/terms/modified"
 * "http://purl.org/dc/terms/subject"
 * "http://xmlns.com/foaf/0.1/depiction"
 * "http://xmlns.com/foaf/0.1/email"
 * "http://xmlns.com/foaf/0.1/familyname"
 * "http://xmlns.com/foaf/0.1/givenname"
 * "http://xmlns.com/foaf/0.1/homepage"


 * synchronized with Person profile?

Third party applications

 * clarify with MPI PL
 * clarify with blogs
 * clarify with Cluster Jus/Contens --Ulla 11:00, 24 November 2009 (UTC)
 * inform Erik as they also use pubitems --Kurt 13:48, 18 February 2010 (UTC)


 * Backward compatible interface will be provided for MPIPL and blogs
 * JUSCMS communicated with Contents

Identifiers from CONE in Publication Metadata
Values of identifiers of things coming from CONE has to be provided as URIs in following manner:


 * person identifiers

urn:cone:persons30

has to be changed with

http://cone.mpdl.mpg.de/persons/resource/persons30

path "/md-records/md-record/publication/creator/person/identifier" ""/md-records/md-record/publication/source/creator/person/identifier"


 * Journal identifiers
 * No change with FOXML now
 * CONE identifier is not into the journal identifiers in publication metadata
 * can not be added with MD transformation due to lookup required to match to CONE IDs and add additional identifier as CONE;
 * future pubman improvement: to also include cone identifier in PubMD


 * DDC identifiers
 * no change with FOXML now,
 * has to be revisited in next release by:
 * adding xsi:type to dc:subject metadata in any case as there would be additional classifications
 * or attempting to insist on using of classifications which have URIs assigned already (in this case we would have to make some changes on MD profile perhaps)
 * no further change required also with Lucene (as originally thought), as it makes no sense
 * e.g. browse by DDC has to send to PubMan a query of DDC local-identifier instead of DDC identifier URI


 * Languages

en

has to be changed with

eng

note: replacement of xsi:type and value

Replacement of data available from core-service live:

"/md-records/md-record/publication/language";"da" => dan "/md-records/md-record/publication/language";"de" => deu "/md-records/md-record/publication/language";"el" => ell "/md-records/md-record/publication/language";"en" => eng "/md-records/md-record/publication/language";"es" => spa "/md-records/md-record/publication/language";"fi" => fin "/md-records/md-record/publication/language";"fr" => fra "/md-records/md-record/publication/language";"it" => ita "/md-records/md-record/publication/language";"ja" => jpn "/md-records/md-record/publication/language";"ko" => kor "/md-records/md-record/publication/language";"ne" => nep "/md-records/md-record/publication/language";"nl" => nld "/md-records/md-record/publication/language";"pl" => pol "/md-records/md-record/publication/language";"pt" => por "/md-records/md-record/publication/language";"zh" => zho

Note: language code stays as three-letter, as this is in any case externally managed identifier