Hi Kerstin and Michele,
Thank you for your
Apologize for the
image didn't go with the email. Let me explain more about my situation
and please give me some advices.
My archives have
just installed the digital repository system and our self-developed archival
catalogue system do not synchronize to the digital repository. Most of
the digital objects in our archives have been digitised from the analogue
collection. They are mainly scanned text documents in TIFF format with
an associated access copy in PDF/A. Some AV collection have also
been digitised too. We planned to ingest these digital objects into our
digital repository. As mentioned our archival catalogue system has been
developed based on ISAD(G) and also consider for users to search with the
finding aids, we think EAD seems more appropriate to adopt and there are
not much description for the digital object. We suppose our digital object
with their embedded technical metadata are good enough. I am a bit confused
now, do you mean I can adopt one more schema at a time for the administrative
and descriptive metadata?
Thanks for introducing
the EAD3 tag library. I have been using this to map with the fields in
my catalogue system exported from our database in an excel format. Since
the data exported from my catalogue system say for an item will also export
both the series level and the deposit level. In generating an XML from
XLS (the exported excel file) may not be a good way. I have also tried
to use Archivespaces as a platform to export an XML in EAD 3, however only
around 70% would be able to map and can only be exported in top level.
This may not be a fast way to convert our data to XML for batch ingestion
too. Do you have any advices?
Please refer to the
that I would like to illustrate in my first email, are that we will import
the file structure as if the records as a series, deposit and item with
the respective XML files. With Kerstin mentioned in her email about digital
object only linking to item level, give me a second thought, should I just
ingest digital objects and the XML in item level rather than illustrated
in my diagram with several layers.
Between I will try
to seek help from our IT colleagues to install the programme and have a
Arnold <[log in to unmask]>
[log in to unmask]
Ingestion into Digital Repository using EAD 3.0
Archival Standards List <[log in to unmask]>
thanks for your email and question. As
Michele mentioned, and due to attachments not coming through via the list,
it would be great if you could explain a little bit more about what your
current situation is, what it is that you intend to do and where EAD3 comes
into the picture as part of your scenario.
From what I understand, I assume that:
to chat in more detail :-)
- You would want to map the descriptive
fields in your self-developed cataglogue, which is based on ISAD(G), with
the EAD3 tag library includes a crosswalk for this purpose, which might
be of help in this: https://www.loc.gov/ead/EAD3taglib/EAD3.html#appendix-AppendixAEADCrosswalks
- You would be looking for a tool that
might help you in transforming this logical mapping into a technical script
that can help you creating the appropriate data for ingestion;
I've never used the following tool myself and it might have developed into
something less flexible during the past years, but colleagues at the National
Technincal University of Athens have created a visual mapping tool that
might be worth checking out: https://github.com/mint-ntua/Mint-Athena
- You would want to connect the digital
objects (TIFFs and PDFs) in your digital repository with the descriptive
metadata from your catalogue;
if that's the case and you would only be looking at the aspect of linking
the digital objects with the descriptions on item level, EAD3 can help
you with that; if you, however, would want to describe the digital objects
themselves, there might - as Michele has pointed out - be other, potentially
better suited formats available.
Kerstin Arnold (she/her/hers)
EAD team lead at Technical Subcommittee
on Encoded Archival Standards
Archives Portal Europe Foundation
Follow us on Facebook,
or via our blog
Find more on our code and use of standards
Am Mo., 20. Apr. 2020 um 19:58 Uhr
schrieb MicheleR <[log in to unmask]>:
4/20/2020 5:18 AM, Athena wong wrote:
> Hi everyone,
> We are thinking to adopt EAD 3.0 schema to map with the descriptive
> our self developed catalogue system for ingestion into the digital
> 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
> start with scratches by mapping the EAD 3.0 with ISAD(G) fields in
> system and produced the required metadata in XML for ingestion, are
> advices or tools recommended for us to start with.
> Your suggestion would be highly appreciated. Thank you.
Hi Athena --
Attachments don't come through on the list, so we can't see your diagram.
online somewhere, so you could provide a URL? As it is, I'm not quite
it is you're doing. Are you saying that you want to use EAD to describe
digital objects, and that the EAD will be ingested by your digital repository
If so, could you explain why you've chosen EAD for this? Not that
work, but there are other schemas that were specifically designed for digital
object description (e.g. MODS) that might be a better match.
Or perhaps you're using EAD for your finding aids, and you want to point
link) to digital objects stored in your repository?
What is needed is a realization that
power without love is reckless and abusive, and
love without power is sentimental and anemic.
Power at its best is love
implementing the demands of justice, and
justice at its best is power
correcting everything that stands against love.
~ Martin Luther King, Jr.