Hi Kim,

thanks for your suggestion. We have harvester that use the generic harvest via 
the ListSets, but we also have harvesters that do a selective harvest of just a 
selection of our dspace collections. At the moment they are harvesting a whole 
list of sets. We are now looking into combining various dspace collections into 
a single set. Any pointers on how to go about that are welcome.

best, Francis


Dr Ir Francis Brouns | Welten Institute - Research Centre for Learning, 
Teaching and Technology | Faculty of Psychology & Educational Sciences | Open 
University of the Netherlands | Valkenburgerweg 177 6419 AT Heerlen | P.O. Box 
2960 6401 DL Heerlen | Phone + 31 45 5762152 | Fax +31 45 5762800 | e-mail 
francis.bro...@ou.nl

From: Kim Shepherd [mailto:kim.sheph...@gmail.com]
Sent: 31 March 2014 21:29
To: Brouns, Francis
Cc: Joan Caparrós; dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] OAI set specification

Hi all, my initial suggestion was going to be using Apache mod_rewrite to 
rewrite the hdl_ portion of the "set"  query value, but now I realise you don't 
know in advance whether it's a collection or a community... (ie. "com" or "col" 
in the new value).. that is tricky.
Depending on the number of communities and collections you have, you could 
still implement this with a series of rules, one per set (instead of a regex 
match/replace), but it doesn't scale very well and needs constant maintenance 
as you add/change your community and collection structure.

Just a note -- your actual OAI endpoint URL isn't really changing, just the set 
ID format... if a OAI harvester does a request?verb=ListSets as normal, they'll 
get back a list of the (new) set IDs and can then harvest them without worrying 
about what they used to be, or will be in future... do you have any harvesters 
that are configured to just come in and harvest particular OAI sets?

Cheers

Kim

On 1 April 2014 03:39, Brouns, Francis 
<francis.bro...@ou.nl<mailto:francis.bro...@ou.nl>> wrote:
Hi Joan,

did you get an answer to your question? We also have this problem, in that our 
harvester URL needs to stay the same as it was before in order for our site to 
be harvested.

best wishes, Francis Brouns



From: Joan Caparrós 
[mailto:joan.capar...@csuc.cat<mailto:joan.capar...@csuc.cat>]
Sent: 28 January 2014 17:17
To: dspace-tech@lists.sourceforge.net<mailto:dspace-tech@lists.sourceforge.net>
Subject: [Dspace-tech] OAI set specification


Hi everybody,
I've notice that in the new OAI (with DSpace versión 3.x) a lot of things have 
changed, I'm worried about the "set" call.
In other versions we did a call like this:
request?verb=ListRecords&metadataPrefix=ese&set=hdl_10687_4
where set hdl_10687_4 was a comunity

now I see that with the new version this call doesn't work and I have to do 
something like this
request?verb=ListRecords&metadataPrefix=ese&set=com_10687_4

I have to save that compatibility because some harvesters already have my old 
comunities sets and now I can't change them.
How can I make to ensure compatibility with the old version calls?

--

.........................................................................



Joan Caparrós

Tècnic de Projectes

Consorci de Serveis Universitaris de Catalunya (CSUC)



Gran Capità, 2 (Edifici Nexus)•08034 Barcelona

T.93 551 6204•F.93 205 
6979•joan.capar...@csuc.cat<mailto:joan.capar...@csuc.cat>

www.csuc.cat<http://www.csuc.cat> •Twitter @CSUC_info•Facebook•Linkedin

Subscriu-te al butlletí; (www.csuc.cat/butlleti<http://www.csuc.cat/butlleti>)

.........................................................................



________________________________
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Open Universiteit sluit iedere 
aansprakelijkheid uit die voortvloeit uit elektronische verzending. Aan de 
inhoud van deze e-mail en/of eventueel toegevoegde bijlagen kunnen geen rechten 
worden ontleend.

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Open Universiteit rules out any and every liability resulting from any 
electronic transmission. No rights may be derived from the contents of this 
message.

------------------------------------------------------------------------------

_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net<mailto:DSpace-tech@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


________________________________
Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan 
en gebruik door anderen is niet toegestaan. Open Universiteit sluit iedere 
aansprakelijkheid uit die voortvloeit uit elektronische verzending. Aan de 
inhoud van deze e-mail en/of eventueel toegevoegde bijlagen kunnen geen rechten 
worden ontleend.

This e-mail is intended exclusively for the addressee(s), and may not be passed 
on to, or made available for use by any person other than the addressee(s). 
Open Universiteit rules out any and every liability resulting from any 
electronic transmission. No rights may be derived from the contents of this 
message.
------------------------------------------------------------------------------
_______________________________________________
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

Reply via email to