ead and Mets in ica-atom

[youpla]

hello,
in order to include digital data( obtained from digitalization or
originally created by computer) in our archives, we choose to use EAD
as container for the major information and a link to one or more mets
files through the <dao> tag in order to be able to authentify data,
identify different versions of same file(original, normalized and for
diffusion), and so on.
I would like to know if you are planning to consider METS and how do
you will consider it?

Thanks for any answer

[Evelyn McLellan]

Hi Youpla,

We are planning to include METS xml import/export functionality in
release 1.1, scheduled for March, 2010. You may be interested in a new
feature for 1.0.8, though - multi-file digital object upload. This
feature (which is now working in our development environment) allows
users to upload batches of digital objects at once, automatically
assigning them to pre-selected parent-level descriptions and creating
derivative images (if appropriate) on upload.

Evelyn

[peterVG]

Hi Youpla,

As mentioned in a previous thread on this question:
http://groups.google.ca/group/ica-atom-users/browse_thread/thread/d6d8e5a23afd2d3c/

We hope to support EAD <dao> tags in the 1.0.8 release and, as Evelyn
mentions above, METS objects in the 1.1 release.

From the description of your use case above it sounds like you would
like the application to be able to trigger a variety of actions or
logic based on the information it is reading in METS files linked
through the dao tag.

However, our initial METS implementation will likely be very basic.
Namely as a way to import and export digital objects along with their
metadata as information packages.

Perhaps your project or institution has the resources (i.e. developers
or funding) to work on that more sophisticated functionality? We'd be
happy to facilitate and collaborate to help you integrate that into
the codebase.

Cheers,

--peter

Peter Van Garderen
ICA-AtoM Software Release Manager

[youpla]

At this time we have no ressources to do that (i am alone to work on
this)
It is not so important to import all the data inside ica-atom.
I can imagine that the processing of METS and digital data is outside
ica-atom
But i must be sure to be able to 'join' the METS file from ICA-ATOM
The EAD file must reference the METS file but the name resolution must
be done through something like an separate xsl that i can modify
because i want to avoid a full path inside the EAD and METS (because
for long term preservation this is not meaningful)
The second part is that it is very important to be coherent between
ICA-ATOM and the long-term preserved data
This means that i have to be sure that i can extract the full
information from ica-atom in a fomat compatible with the principes of
long-term conservation:
- no absolute link (no http://...) in the EAD and METS concerning data
- linked information must be extracted(ISAAR information extracted
with EAD information) with the EAD file to obtain a set of data which
must be complete and coherent
- EAD mand METS as xml text file
and so on

sorry if my english is not perfect
if you want more fine description you can contact me

regards