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 >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
