In the past I have used this element as a wrapper to contain records input/output from/by ad hoc XSL transformations. E.g. converting a number of MODS records to Dublin Core with a single XSLT. Much easier to work on a single modsCollection document than multiple MODS files.
The advantage to having such a wrapper element included in the specification is that it validates against the schema.
Maybe others use it in a more systematic way -- I can imagine API calls to a system that outputs lists of MODS files (other than OAI-PMH). The result of such a search could equally be a single record (as you have seen in your example) or thousands.
Joseph Greene, MLIS
Research Repository Librarian
Level 2, James Joyce Library
T: +353 1 716 7398 | E: [log in to unmask] | W: http://researchrepository.ucd.ie/
[log in to unmask]" alt=mailLogo>
www.ucd.ie/library | libguides.ucd.ie | @UCDLibrary
From: Metadata Object Description Schema List [mailto:[log in to unmask]] On Behalf Of Lucy McKenna
Sent: 19 September 2016 13:04
To: [log in to unmask]
Subject: [MODS] modsCollection Root Element Use
My apologies in advance if this is not the appropriate forum in which to ask my question.
I am a new user of Mods and I was wondering how and when exactly is it appropriate to use the modsCollection Root element?
Would this element contain multiple mods root elements? And should the records within the collection be part of a series, or can the relationship be that the records have the same subject or genre? Or indeed, could the records in the collection be arbitrary?
I have seen some sample records where there is only a single mods record with a modsCollection root element, hence my confusion regarding its appropriate use.
Thank you for your help,