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 arbitrarily, so I thought I would ask. If there are reasons for keeping for keeping the caption at 255, then I think it makes sense to truncate it in the importer, rather than just having things die on a database error.
I currently use a modified version of Mark Custer’s schematron <https://github.com/fordmadox/schematrons/blob/master/ArchivesSpace-EAD-validator.sch> to check EADs prior to import, and can certainly add code to check <dao> @titles. The problem with doing that is the double use of @title for both digital_object:title and file_version:caption. Since ASpace supports long titles, and the archivist presumably assigned a long title for a reason, I would hate to shorten it before import just to make sure that it fits when re-used as a caption. Thanks, Brian > On May 24, 2018, at 5:25 PM, Timothy Dilauro <ti...@jhu.edu> wrote: > > 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 restrictions ahead of EAD > import attempts. In that manner, those non-conformant captions (and anything > else you check on) could be tweaked before import. > > Cheers, > ~Tim > >> On May 23, 2018, at 2:39 PM, Brian Harrington <brian.harring...@lyrasis.org> >> wrote: >> >> >> Currently when importing an EAD, <dao>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 <dao>s with @titles longer than 255 characters. These titles >> are OK for digital_object:title, which is VARCHAR(8704) but too long for >> file_version:caption, which is VARCHAR(255). So the import fails. >> >> Should this be considered a bug? If it is, and if one were theoretically >> considering a PR, would it make more sense to harmonize the length of the >> title and caption, or truncate the caption to 255 characters? My >> inclination is just to increase the maximum length of captions, and rely on >> people to show restraint, but I know that other people might have different >> opinions. >> >> Thanks, >> >> Brian >> >> -- >> Brian Harrington >> Migration Specialist >> LYRASIS >> brian.harring...@lyrasis.org >> skype: abbistani >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
