_Group] EAD Importer and DAOs
Hi Brian,
I don't think it's a good idea to change the data model just to avoid imports
failing, though there may be other rationales that result in such a change.
In the mean time, it might be useful to write some XSLT or some other custom
code to perform sanity
IIRC, also, a lot of the smaller DB-level defaults (and some of the larger
ones) are the result of various defaults or arbitrary guesses - before just
saying that it's part of the data model and we should just live with it, one
should always positively verify that it's legitimately part of the
Hi Tim,
I agree it seems a bit backwards to change the data model to suit the importer,
which is one of the reasons I decided to pose the question to the list. There
could be valid reasons (display issues?) for limiting the length of the
caption, but these things are often assigned somewhat
Hi Brian,
I don't think it's a good idea to change the data model just to avoid imports
failing, though there may be other rationales that result in such a change.
In the mean time, it might be useful to write some XSLT or some other custom
code to perform sanity checks relative to ASpace
Currently when importing an EAD, s are used to create digital objects. As
part of this process, the @title attribute is used for both the digital object
title, and the caption under file versions. I've recently run into a fun issue
with s with @titles longer than 255 characters. These titles
