InstallItem.installItem registers identifiers and *then* calls populateMetadata. This means that IdentifierProviders can't depend on the values of dc.date.accessioned and dc.date.available when crosswalking to generate metadata for an identifier submission.
This kind of makes sense at the moment, because an exception thrown by IdentifierService is treated as fatal to the installItem operation. Is there some reason why we should not just note such an exception and go on? Is there some reason why we should not place the identifier registration after populateMetadata, or even after finishItem? -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
