Hello, I'm doing quite a few AIP imports on to prepare for a big migration we have coming up and I was wondering how the XSD caching mentioned on the wiki[0] works. I spent some time finding and downloading the correct .xsd files (which is harder than it sounds) and added the changes to dspace.cfg, but after doing a few rounds of testing I'm not sure it actually works.
First of all, the time to import a small collection hierarchy with ~200 items was the same with and without the XSD caching. Second, I did a tcpdump during the import to see if I could track the repeated downloading of XSD files for METS validation, but I only saw ~200 pings—one for each iteration of the ingest loop!—to an update server belonging to one of the Java components used in the AIP logic (which is both inefficient and a violation of privacy, a subject for another time). Does anyone have any insight? DSpace version is 5.5. Thanks. [0] https://wiki.duraspace.org/display/DSDOC5x/AIP+Backup+and+Restore#AIPBackupandRestore-AIPConfigurationsToImproveIngestionSpeedwhileValidating -- Alan Orth [email protected] https://picturingjordan.com https://englishbulgaria.net https://mjanja.ch -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
