On Tue, Feb 4, 2014 at 4:39 PM, Shawn M. Kiewel <smkie...@gmail.com> wrote: > > On Feb 4, 2014, at 10:11 AM, helix84 <heli...@centrum.sk> wrote: > >> On Mon, Feb 3, 2014 at 6:35 PM, Shawn M. Kiewel <smkie...@gmail.com> wrote: >>> Is there a way to have “external” items in a DSpace repository? I have a >>> large number of digital objects (our electronic theses and dissertations) >>> that are already being made available by another site, but we’d like to see >>> them as objects in our institutional repository. However, we don’t want to >>> duplicate the digital objects themselves by importing them all into DSpace. >>> So ultimately, we’d like to include each item as its own record with a link >>> to the external location instead of a link to the pdf itself. >> >> Hi Shawn, >> >> let's analyze your needs first. I'll assume you want a searchable >> repository of items stored and maintained somewhere else. You want to >> avoid copying the items because want to keep them in sync - changes >> should be made only to the source repository. > > > Yes, that is correct. > > >> >> It's logical that if you want a searchable repository, you do have to >> copy all the metadata. So you do want each of them as a new item in >> your DSpace and you now have to solve the problem of master-slave >> replication. There are many ways how you can do this, but in order to >> chose the best way we have to know how your source repository is able >> to export the items. E.g. if it supports OAI-PMH, it should be >> relatively easy. You would set up DSpace to harvest your source >> repository, which would also take care of updates to existing items. >> So what software does your source repository use and which export >> methods does it support? > > > It is a homegrown PHP MySQL application that I can write an exporter for. It > doesn’t currently support OAI-PMH. The direction I was leaning was running a > nightly batch to update DSpace with the new items, as we have an nightly > export script for the application that DSpace should be replacing that grabs > all changed records already, so adapting that script to do, say, a SWORD > deposit into DSpace seemed to be the easiest solution to me. Well, it did, > until I couldn’t figure out how to do metadata only… > > Shawn
Even easier for you will be to prepare a .csv export in the DSpace format. It's metadata-only, fast and you can call it from shell: https://wiki.duraspace.org/display/DSDOC4x/Batch+Metadata+Editing Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
