Hi there, We’re on DSpace 3.1 and have just switched over to XMLUI. All we know about DSpace we learned from a 2-day workshop and from working through this XLMUI switch, so please bear with us!
Currently we have our XOAI feed set up such that it effectively excludes items from two collections: · “Restricted thesis” collection – theses accessible to our own staff and students only. Items have anonymous READ access, but bitstreams are restricted · “Symplectic” collection – intended as a dark archive of copyrighted material kept for internal purposes. Items and bitstreams are all access-restricted. Firstly, we’ve noticed that while this excludes the items from ListIdentifiers and from ListRecords, the metadata for the “Symplectic” collection is still returned in a GetRecord request if you know the handle. (It isn’t returned in the “Restricted thesis” collection.) This is unexpected and very undesirable for us. Can anyone explain it and/or suggest a way to ensure this doesn’t happen? Secondly, we’d like to move to a situation where: · “Restricted thesis” collection is included (at least in one OAI context – this is so we can harvest it into our library’s discovery layer Primo) · “Symplectic” collection remains excluded from OAI Our current settings: 1. We have dspace.cfg to: harvest.include.restricted.oai = false We understood this to mean that only items with anon READ would be exposed to OAI, however it’s since been suggested that this has nothing to do with XOAI, and indeed our experience showed no result to switching this between true and false. 2. We also have <Filter refid=”bitstreamaccessFilter” /> on our OAI context (Before I continue, whenever we make a change in dspace.cfg or xoai.xml and related files we are then stopping/restarting dspace and then running the “dspace oai import -cv” job. If this isn’t sufficient to pick up our changes and refresh the cache and we should be doing something else, or doing things in a different order, please let us know, as this may explain everything!) After some changing settings back and forth in our Dev environment we’ve managed to get a situation precisely opposite to what we want, but not in a way that’s very enlightening, and also with no idea how we got there as our settings are now the same as when we started but our results aren’t. Here is a chart I’ve entitled “OAI matrix of woes”: Context Verb # Items in: All # Items in: Restricted theses (items have anon READ; bundles/bitstreams are restricted) # Items in: Symplectic (items and bundles/bitstreams are restricted) request (bitstreamaccessFilter) ListIdentifiers 3705 1888 105 ListRecords 1863 8 105 GetRecord returns record returns record if bundle TEXT anon READ (and other bundles/bitstreams restricted); otherwise does not exist does not exist custom (no filter) ListIdentifiers 5712 1888 106 ListRecords 5712 1888 105 GetRecord returns record returns record returns record How can we: · (As in our first question) Make ListIdentifiers, ListRecords, and GetRecord all behave the same in terms of access? · Include items in the feed where the item has anonymous READ, even if some or all of the bundles and bitstreams are restricted? · While excluding items where the item is restricted? Thanks very much for any clues! Nāku noa, nā Deborah Fitchett Senior Advisor, Digital Access Library, Teaching and Learning p +64 3 423 0358 e deborah.fitch...@lincoln.ac.nz<mailto:deborah.fitch...@lincoln.ac.nz> | w library.lincoln.ac.nz<http://library.lincoln.ac.nz/> Lincoln University, Te Whare Wānaka o Aoraki New Zealand's specialist land-based university ________________________________ P Please consider the environment before you print this email. "The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system."
------------------------------------------------------------------------------
_______________________________________________ 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
