Thank you so much. You explanation is really clear and helpful for me to understand the rationale behind.
I will give a try and hope to find the best way for my archives.
Take care too.
From: Kerstin Arnold <[log in to unmask]>
To: [log in to unmask]
Date: 24/04/2020 16:45
Subject: Re: Ingestion into Digital Repository using EAD 3.0
Sent by: Encoded Archival Standards List <[log in to unmask]>
thanks very much for the further information and the visualisation of your work scenario, and apologies for not getting back to you about this earlier.
Thanks as well to Xavier for the additional input.
Given your explanation, Athena, I would say you can focus on EAD3, even though MODS or METS in general could be good combinations. But as you don't intend to create/add lots of descriptive, administrative or technical metadata to the digital objects themselves, EAD3 would probably be able to provide you with what you need for now.
I'm assuming, that the digital objects in your digital repository already have unique - and maybe even persisten - identifiers/URIs/links which you can use to connect them with the descriptive metadata. On the other hand, there are two elements in EAD3, which you could use to include these identifiers/URIs/links: <dao> (Digital Archival Object) and <daoset> (Digital Archival Object Set). You can use both of them independent from each other or - theoretically - together with each other on each description level, might that be - as in your case - "series", "deposit" or "item". You can also repeat both elements and both elements come with an optional <descriptivenote> element, just in case you would want to add general descriptive information with regard to the digital objects.
In your scenario, you could maybe consider the following encoding (not saying that this is the only - or the ideal - solution, just to show you one example as an option):
<unitid>Reference code of the item</unitid>
<unittitle>Title of the item</unittitle>
<!-- ...any other descriptive metadata for the item... -->
<dao daotype="derived" href="[identifier/URI/link to the first TIFF file]"/>
<dao daotype="derived" href="[identifier/URI/link to the second TIFF file]"/>
<dao daotype="derived" href="[identifier/URI/link to the third TIFF file]"/>
<!-- ...any more TIFF files for this item... -->
<dao daotype="derived" href="[identifier/URI/link to the PDF/A file]"/>
As for your question on which level(s) to ingest the digital objects and the XML for the descriptive metadata: this depends on
I realise, this answer will probably be too loose for you to to walk away and work with directly, but this flexibility in adapting the use of EAD to your own requirements is one of the advantages that this standard has :-)
- what you want to represent within your digital repository,
- how you want to use the data/information that you will eventually hold in your digital repository, and
- the technical possibilities that you have with your system and at your institution.
Hope this is of help.
Best wishes and stay safe,
Am Do., 23. Apr. 2020 um 20:47 Uhr schrieb Xavier Agenjo Bullon <[log in to unmask]>:
I’m writing to you from DIGIBÍS, a Spanish company which has developed an archival management system, DIGIARCH, which is implemented in these projects:
- Galician Digital Archive (https://arquivo.galiciana.gal/arpadweb/es/inicio/inicio.do)
- Norman Foster Foundation Archive (http://archive.normanfosterfoundation.org/en/inicio/inicio.do)
- Felipe Gonzalez Foundation Archive (https://archivo.fundacionfelipegonzalez.org/es/inicio/inicio.do)
DIGIARCH allows for displaying and exporting records of units of description in both ISAD (G) and EAD3. You can check some examples in these links:
- http://arquivo.galiciana.gal/arpadweb/gl/consulta/registro.do?id=337797&formato=ead&aplicar=Aplicar / http://arquivo.galiciana.gal/arpadweb/gl/consulta/registro.do?id=337797&formato=ficha&aplicar=Aplicar
- http://archive.normanfosterfoundation.org/es/consulta/registro.do?id=7221&formato=ead&aplicar=Aplicar / https://archive.normanfosterfoundation.org/es/consulta/registro.do?id=7221&formato=ficha&aplicar=Aplicar
- https://archivo.fundacionfelipegonzalez.org/es/consulta/registro.do?id=81569&formato=ead&aplicar=Aplicar / https://archivo.fundacionfelipegonzalez.org/es/consulta/registro.do?id=81569&formato=ficha&aplicar=Aplicar
DIGIARCH also allows for sending records of units of description in EAD3 through OAI-PMH repository:
Finally, you should know that Galician Digital Archive has registered his own METS profile in EAD3 in the Library of Congress: Galiciana: Digital Archive of Galicia - General Digital Object Profile (http://www.loc.gov/standards/mets/profiles/00000046.xml). You can also check it at https://github.com/SGA-AEP/mets-profile.
I hope that this information was interesting to you!
Xavier Agenjo Bullón
Director de Proyectos
Fundación Ignacio Larramendi
Alenza, 4, 5º
Telf.: (34) 91 432 10 42
Fax.: (34) 91 432 11 13
Certificado ISO 9001.
No imprimir si no es necesario. Protejamos el Medio Ambiente.
En cumplimiento de la LOPD y la LSSI, le informamos de que sus datos personales son incorporados a un fichero, titularidad de la Fundación Ignacio Larramendi, con el fin de ofrecerle información sobre servicios que pueden ser de su interés. Podrá ejercitar sus derechos ARCO (de acceso, rectificación, cancelación y oposición) mediante un escrito dirigido a [log in to unmask], con copia del DNI o documento identificativo sustitutorio.
En caso de querer darse de baja pinche aquí.
De: Encoded Archival Standards List <[log in to unmask]> en nombre de Athena wong <[log in to unmask]>
Enviado: lunes, 20 de abril de 2020 11:18
Para: [log in to unmask] <[log in to unmask]>
Asunto: Ingestion into Digital Repository using EAD 3.0
We are thinking to adopt EAD 3.0 schema to map with the descriptive metadata in our self developed catalogue system for ingestion into the digital repository.
Our ingestion structure will be mainly TIFF files in a single folder for an item level and an access copy (in PDF format) illustrated in the diagram below. To start with scratches by mapping the EAD 3.0 with ISAD(G) fields in our catalogue system and produced the required metadata in XML for ingestion, are they any advices or tools recommended for us to start with.
Your suggestion would be highly appreciated. Thank you.
Assistant Curator (Digital Archive)
Government Records Service, Hong Kong