However, if they aren't actually a collection, this will cause a problem for the importer. So.. it would be nice if SAFBuilder could query the collections to ensure they are collections... Perhaps as a post generation check
Then from that, look up: http://kb.osu.edu/dspace/handle/1811/686, then try to guess where the DSpace REST API might be, and query that, to see if this handle is of type collection?
A new feature of SAFBuilder is the ability to batch import to multiple collections. (Also requires modifying DSpace ItemImport, done for Longsight code, perhaps contributable upstream in DSpace 6 -- https://github.com/LongsightGroup/DSpace/commit/c14db3702b317f1d8dd72d7735a7cccf480f2f99)
collection 123/2233||123/2334||123/3434
However, if they aren't actually a collection, this will cause a problem for the importer. So.. it would be nice if SAFBuilder could query the collections to ensure they are collections... Perhaps as a post generation check
I'm thinking it could query the handle REST API: http://hdl.handle.net/api/handles/1811/686
Then from that, look up:
http://kb.osu.edu/dspace/handle/1811/686
, then try to guess where the DSpace REST API might be, and query that, to see if this handle is of type collection?http://kb.osu.edu/rest/handle/1811/686
In which case, we learn that 1811/686 is a community, and SAFBuilder could complain.