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
www.csuc.cat  .Twitter @CSUC_info.Facebook.Linkedin
Subscriu-te al butlletí; (www.csuc.cat/butlleti)
.........................................................................



------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&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

Reply via email to