mets / mets-board Goto Github PK
View Code? Open in Web Editor NEWDocuments and wiki pages relevant to the business of the METS Editorial Board
Documents and wiki pages relevant to the business of the METS Editorial Board
We should update this with instructions for submitting schema change requests. It is linked from http://www.loc.gov/standards/mets/mets-schemadocs.html
Dear All,
Would it also be possible to include RDF as a recognised MDTYPE attribute value? At present we are placing this as follows MDTYPE="OTHER"
OTHERMDTYPE="RDF" but as we use RDF in all our METS documents it would be nice to have this as a recognised value so that we could place it as follows...
<METS:mdWrap MDTYPE="RDF">
<METS:xmlData>
<rdf:RDF>
<rdf:Description>
<!--RDF Metadata-->
</rdf:Description>
</rdf:RDF>
</METS:xmlData>
</METS:mdWrap>
Regards,
Vicky
National Library of Wales
I’m responsible for digitization at the national library of Luxembourg, as well as our delivery platform. We are using METS/ALTO for digitizing newspapers, postcards, posters, manuscripts and books and have developed our own viewer for displaying METS/ALTO objects on the web. This viewer is open source and is currently also used by the national library of Latvia and the university library of Belgrade in Serbia. I think it would also be interesting to list it on the METS tools page at http://www.loc.gov/standards/mets/mets-tools.html under the METS Presentation (non-commercial) heading.
The software is called “bnlviewer” and it’s main page is at sourceforge: http://sourceforge.net/projects/bnlviewer/
Here is the short description from the sourceforge page:
Viewer for METS (http://www.loc.gov/standards/mets/) files with OCR files in the ALTO format. The viewer needs a tomcat application server to run in. It can be deployed so that it reads the METS files from a local folder. Its main use is for digitized newspapers and postcards but can be adapted to other METS profiles as well. The viewer can be seen in action at: http://www.eluxemburgensia.lu
I would be grateful if you could add it.
"working with our non-registered profile of METS I have encountered a need of being able to type the note in agent so it would be possible to say what kind of information the note have. Have gotten the same comment from some other collegues also working with it. So perhaps the xsd:anyattribute could be made possible here too so the schema dont have to handle the typing of the note with attributes type and othertype (setting up the valuelist for type, well not to easy)?"
From Karin's note to METS-Board of Sept. 6.
This used to be on the SocialText wiki, but it doesn't seem to be there anymore. We would like to host this document on the GitHub site, and correct the link from the LoC METS web site.
https://www.loc.gov/standards/mets/mets-examples.html
I notice that when I click the bottom 'Home' link, it send you to https://www.loc.gov/folklife/ rather than https://www.loc.gov/standards/mets/mets-home.html - which is the target of the Home link at the top of the page.
Best,
Kieran O'Leary
National Library of Ireland
As reviewed the Rosetta Mets structure (below link), found that no option available for creating article metadata.
http://www.loc.gov/standards/mets/profiles/00000042.xml
It was mentioned as "Only one level for IE level" & "One level for file (page) level", if more than one articles present in the single page, then how can we structure. Kindly let us know any possibilities.
Thanks,
Rajasekaran A.
The METS div element allows xlink:label, but the XLink spec does require xlink:type in this case (https://www.w3.org/TR/xlink11/#xlinkattusagepat). It seems like the purpose of having the xlink:label on the div is to allow reference from smLink elements, so I think this is a "resource"-type element (https://www.w3.org/TR/xlink11/#local-resource) and we could include the "resourceLink" attribute group from the XLink schema.
This could cause problems if adding that attribute group causes validation to fail for existing documents, so we should verify behavior.
The schema requires that the links are included in an xlink:href element rather than in the body of the element. However, the METS overview (https://www.loc.gov/standards/mets/METSOverview.html) has:
<dmdSec ID="dmd001">
<mdRef LOCTYPE="URN" MIMETYPE="application/xml" MDTYPE="EAD"
LABEL="Berol Collection Finding Aid">urn:x-nyu:fales1735</mdRef>
</dmdSec>
<file ID="FILE001" ADMID="AMD001">
<FLocat LOCTYPE="URL">http://dlib.nyu.edu/press/testimg.tif</FLocat>
</file>
<fileSec>
<fileGrp ID="VERS1">
<file ID="FILE001" MIMETYPE="application/xml" SIZE="257537" CREATED="2001-06-10">
<FLocat LOCTYPE="URL">http://dlib.nyu.edu/tamwag/beame.xml</FLocat>
</file>
</fileGrp>
<fileGrp ID="VERS2">
<file ID="FILE002" MIMETYPE="audio/wav" SIZE="64232836"
CREATED="2001-05-17" GROUPID="AUDIO1">
<FLocat LOCTYPE="URL">http://dlib.nyu.edu/tamwag/beame.wav</FLocat>
</file>
</fileGrp>
<fileGrp ID="VERS3" VERSDATE="2001-05-18">
<file ID="FILE003" MIMETYPE="audio/mpeg" SIZE="8238866"
CREATED="2001-05-18" GROUPID="AUDIO1">
<FLocat LOCTYPE="URL">http://dlib.nyu.edu/tamwag/beame.mp3</FLocat>
</file>
</fileGrp>
</fileSec>
Hello all,
We have our first attempt at a METS profile for the UNTL METS Archival Information Package Profile.
This document is available publicly at the following URL - https://github.com/unt-libraries/untl-mets-aip/blob/master/untl-aip-mets.xml
Please let us know if there is anything we should clarify or if there are omissions or if there is incorrect usage of fields.
Thank you for your consideration.
Mark Phillips
Assistant Dean for Digital Libraries
UNT Libraries
Can you please exchange the link to our website on the site http://www.loc.gov/standards/mets/mets-tools.html in section
METS Creation Services (commercial digitization services providing METS output)
From
http://www.ccs-digital.info/en/products/conversion-services
we are interested in registering METS profile for National Digital Library of the Czech Republic.
Please, find the attachment.
Neither PREMIS 3 nor EAD 3 reference XLink. This would resolve several of the XLink related issues: #30, #33, #19.
I will draft a revision of the METS schema that:
xlink
namespace qualificationxlink
namespace to validateHello,
Please find attached updated version of the Ex Libris Rosetta METS Profile, to replace the version posted here.
Please let me know if you have any questions or comments.
Best Regards,
Opher Kutner
Rosetta, Alma Business Analyst
Tel: +972-2-6499218
[email protected]
This is a very old document, and there are likely several things that need to be updated or corrected.
Hi Tom,
Thank you very much for the information.
I have looked over the profile and I have realized it is only described in Spanish, so I am attaching a document which describes the same profile that I sent to you before in both English and Spanish. I would be grateful if you could replace the previous profile with the attached to this email.
Sorry for the inconvenience.
Kind regards,
The documents, http://www.loc.gov/standards/mets/mets-schemadocs.html, need to be updated to reflect the current version of the schema:
METS Schema 1.9 Documentation
METS Schema 1.9 METS Structure Diagram
METS Version 1 namespace page: information about the version 1 target namespace URI
Hi all,
Have just discovered that in the primer the xlink:type attribute isn't mentioned together at all with xlink:href. All the other attributes are listed but not that and its mandatory in the used xlink-schema and in the xlink-standard (as I have understood it). Got the comment that since its not mentioned so therefore its thought not to be used and they run into validation problems.
So can we update the text?
Best,
Karin
Hi, not sure if this is the correct place to put this, but I noticed that the overview: https://www.loc.gov/standards/mets/METSOverview.v2.html#descMD
possible contains an invalid example for <mdref>
The XSD and METS Primer both say that <mdref>
is an empty element, and the xlink
attribute should be used to store a value.
The overview has this example:
<dmdSec ID="dmd001">
<mdRef LOCTYPE="URN" MIMETYPE="application/xml" MDTYPE="EAD"
LABEL="Berol Collection Finding Aid">urn:x-nyu:fales1735</mdRef>
</dmdSec>
:
which has urn:x-nyu:fales1735
as a value
This is the output of the validation
xml val -e --xsd mets.xsd mets1.xml
mets1.xml:23.19: Element '{http://www.loc.gov/METS/}mdRef': Character content is not allowed, because the content type is empty.
mets1.xml - invalid
Dear METS Editorial Board,
I just wanted to let you know that
https://www.loc.gov/standards/mets/mets-tools.html contains some broken links, such as
How comprehensive should the list be considered?
Kind regards,
Federico Leva
From Board call http://www.loc.gov/standards/mets/METSPrimer.doc
Dear Betsy & Thomas,
I trust this message finds you both well, and I hope you are having a good week thus far. I was referred to contact you by contacts at the Library of Congress regarding Apex’s interest in being added as a commercial supplier for METS/ALTO. Specifically, in regards to the list of suppliers found at the METS website. Apex has been actively supplying METS/ALTO deliverables for a number of years to national libraries and state newspaper programs. We have served as a conversion supplier since the start of the NDNP program well over a decade ago and continue to convert newspapers for dozens of institutions around the globe. Please let me know if you have any questions for me regarding Apex, I look forward to corresponding with you further. Thank you for your consideration.
Best regards,
Joel
Currently it's only on the LoC web site: http://www.loc.gov/standards/mets/METSOverview.v2.html
@karinbredenberg reports:
Have read the text and the extended is used in the
smLink
but I see that the type attribute isn't in the mets schema so there is more needed to be done in that case.
It looks like we are specifying a list of allowed attributes directly in the METS schema for smLink
rather than one of the XLink attribute groups from http://www.loc.gov/standards/xlink/xlink.xsd. It seems like the intention is that it have xlink:type="arc"
, but smLink
also requires the xlink:from
and xlink:to
despite those being optional in the XLink spec (https://www.w3.org/TR/xlink11/#xlinkattusagepat).
I'm not sure what the best way to get the default value for xlink:type="arc"
or even just to require xlink:type
at all for smLink
is while still retaining xlink:from
and xlink:to
as required attributes. The easiest option might just be to allow xlink:from
and xlink:to
to be optional on smLink
; then we could remove all the explicitly-declared XLink attributes for smLink
in the METS schema and just add the xlink:arcLink
attribute group.
See https://github.com/mets/METS-board/wiki/2021-06-03-Board-Meeting-Notes#mdgrp--filegrp
Is it possible to have md directly under mdSec / file optionally directly under fileSec? We don't want to remove grouping entirely, and anything for mdSec should be parallel with fileSec. If possible, we should avoid mixing md/mdGrp under mdSec and likewise for file/fileGrp/fileSec.
There are certainly cases where it might be unnecessary to have fileGrp and mdGrp. Processing software might be more complicated if the group structure is optional, and especially if mixing is allowed.
Making mdGrp optional could be useful if it helps avoid multiple IDREFs and the need to tokenize IDREFs.
We will draft something for making the nesting optional, and make sure it is possible to prohibit mixing mdGrp and md at the same level, and fileGrp / file at the same level.
We should review the list of tools http://www.loc.gov/standards/mets/mets-tools.html and move it to a GitHub wiki so that it is easier to keep the list of tools up to date.
Galiciana_Digital_Archive_of_Galicia.docx
We have developed an Archives Digital Project, Galiciana: Digital Archive of Galicia, in which 34 Archives from Galicia participate, and we have also defined our own METS profile for Archival Digital Objetcs. We are interested in adding our Project to the METS Implementation Registry and registering our METS profile with the Library of Congress Network Development and MARC Standards Office, as well.
Hi all,
I got a mail by Marco Klindt of the Zuse Institute Berlin who pointed out an outdated information in the METS overview at http://www.loc.gov/standards/mets/METSOverview.v2.html#structlink. The last example in the “Structural Links” section uses the attributes “to” and “from” although it is “xlink:to” since METS 1.5.
Maybe we should check if there are other outdated parts in the overview.
Tobias Steinke
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.
Thomas,
It was pointed out that the URL no longer works for the UF METS editor tool on this page: http://www.loc.gov/standards/mets/mets-tools.html
Can you correct the name and URL?
The name should be: SobekCM METS Metadata and Viewer
The correct community-maintained URL is: http://sobekrepository.org/software/mets
Many thanks!
Mark V. Sullivan
Primary developer of SobekCM METS Tool
Previously with the University of Florida Libraries
See this commit for the change request: b78ee53
I send you our Mets Profile for the Spanish Virtual Library of Bibliographical Heritage (Biblioteca Virtual del Patrimonio Bibliográfico) for review and subsequent registration in the Library congress METS-profile website.
I'd like to submit an entry to the METS registry on behalf of the German Literatur Archive. I hope I got all the information right. If not or if you have further questions, please let me know.
Please find the information below.
Stephanie Kuch
Development
Deutsches Literaturarchiv Marbach
Deutsches Literaturarchiv Marbach - German Literature Archive Marbach
Description:
In 2013 the German Literature Archive in Marbach launched the three-year project „Preserving German Net Literature And Making It Long-Term Available“.
The purpose of this project was to establish a corpus of relevant sources of German-language electronic literature developing since the 1990s. This type of literature uses the internet and its typical hyperlink structure not only as a form of publication, but also as a scope of design and object of aesthetic reflections. Software and hardware are of paramount importance to the creation and reception of electronic literature. METS is used to store bibliographical, technical and structural information about the archived objects.
Dates:
In production, ongoing
Sites:
All archived objects and their respective METS files can be accessed via SWBcontent http://literatur-im-netz.dla-marbach.de/
Profiles:
Status: Completed and registered. Application profile available at https://wwik-prod.dla-marbach.de/line/images/f/f1/Application_profile_V3_en.pdf
Registered URI(s):
https://wwik-prod.dla-marbach.de/line/images/f/f1/Application_profile_V3_en.pdf
Docs:
None
External schema:
dmdSec: mods http://www.loc.gov/mods
techMD: premis https://www.loc.gov/standards/premis/
sourceMD: none
rightsMD: mods http://www.loc.gov/mods
digiprovMD: none
Docs:
none
Tools:
DLAB, a Bag creator that creates an AIP in the BagIt format and the respective METS file. Available on GitHub: https://github.com/netzliteratur/dlab
Contacts:
Stephanie Kuch: [email protected]
Department for archiving electronic literature: [email protected]
"the METSRight schema I've have gotten questions regarding changes it from the Archives Portal Europe Foundation. Or more they planned to change the schema and use values from the Europeana rights statments instead of the ones present in the schema as typing of the rights and I said well it wont be the METSRights schema if you do that, it wont validate with the original schema and all those ususal comments of using a standard. They have for now decided to use the othertyping-attribute but there will come more from them as I understood the conversation and they want to change the METSRights schema. We need to put something up regarding it, who owns it, if we recommend the use and so on. And not to forget it is used in registered profiles so something needs to be done I guess."
From Karin's note to METS-Board of Sept. 6
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.