METS profile submission for the software Pleade

[thabing]

https://github.com/mets/wiki/blob/master/METSProfiles/00000042/profil-pleade-mets.xml

To whom it may concern in the METS Editorial Board:

At our company, AJLSM, we provide many libraries, genealogists and archivers here in France with a tool called Pleade. It is used to make METS, ALTO, EAD and other XML documents searchable on the Internet with their corresponding photos, content and metadata. METS is an important part of our software for transferring data from one application to another, gathering data from various sites, and storing new information. We would like to submit our METS profile so that our clients here in Europe can better understand how to generate METS documents that interact well with our application.

I have attached a document profil-pleade-mets.xml for you to consult. We appreciate you setting up a place for us to share our information with the community and the world.

Thank you for your consideration.

[karinbredenberg]

Where can I find the profile document?

[thabing]

Hi Karin,

We haven’t yet registered this profile. I just added it to our GitHub wiki repo, and I added a link at the top of the issue to it: https://github.com/mets/wiki/issues/5

Regards, Tom

From: Karin Bredenberg [mailto:notifications@github.com] Sent: Tuesday, May 27, 2014 2:26 AM To: mets/wiki Cc: Tom Habing Subject: Re: [wiki] METS profile submission for the software Pleade (#5)

Where can I find the profile document?

— Reply to this email directly or view it on GitHubhttps://github.com/mets/wiki/issues/5#issuecomment-44243074.

[karinbredenberg]

Thanks!

[thabing]

The following was sent to the submitters on May 29; the Board has not received any followup:

Apologies for the long delay. The METS Board has started to review your profile submission, and there are some minor syntactic problems with it:

1) The mdWrap element has an invalid value of 'BMO-CSV' for the MDTYPE attribute:

<METS:mdWrap ... MDTYPE="BMO-CSV" ... >

The MDTYPE attribute currently only allows these enumerated values: MARC, MODS, EAD, DC, NISOIMG, LC-AV, VRA, TEIHDR, DDI, FGDC, LOM, PREMIS, PREMIS:OBJECT, PREMIS:AGENT, PREMIS:RIGHTS, PREMIS:EVENT, TEXTMD, METSRIGHTS, ISO 19115:2003 NAP, EAC-CPF, LIDO, OTHER

I would recommend that you instead use the value of OTHER, and then put BMO-CSV in the OTHERMDTYPE attribute:

<METS:mdWrap ... MDTYPE="OTHER" OTHERMDTYPE="BMO-CSV" ... >

Alternately, if BMO-CSV is a widely-used, standard metadata scheme, the METS Board would consider adding it as one of the enumerated values in a future revision of the METS schema. For this to happen, you would need to provide a pointer to the standard XML schema for BMO-CSV along with some sample XML documents conforming to the schema. We would generally only consider this for schema that have the backing of some standards setting body.

2) The second syntactic error is that values used for the div element ID attributes do not conform to the XML standard for the ID data type. XML ID values must be valid NCNAMEs. In general this means they must start with a letter or underscore and cannot contain colons, http://www.schemacentral.com/sc/xsd/t-xsd_ID.html.

For example, this is not valid because it starts with a number and it contains colons:

ID="100779:1:NP"

But, one of these would be valid:

ID="_100779_1_NP" or ID="DIV_100779_1_NP"

If you can correct these syntactic errors and send me a new copy of the profile, we can submit it for wider review. Once we get a syntactically valid profile document, we should be able to get it published in a few weeks.

Let me know if you have any questions.

Kind regards, Tom Habing Technical co-chair, METS Editorial Board

[thabing]

Issue being closed. There has been additional correspondence or feedback from the original requester for over four years.