Hello,
Thank you very much for your help.
We would like to find a way to hide embargoed items (metadata +
bitstream) completely, also from bots and APIs. However, neither the
embargo nor the "private flag" nor a combination of both seems to be
sufficient:
https://wiki.duraspace.org/display/DSDOC5x/DSpace+Item+State+Definitions:
Embargoed items
"If the metadata of the item should be visible only to a specific group
of users, it is possible to define an embargo policy also for the ITEM
itself. A READ policy for a specific group will mean that only the
users in that group will be able to access the item splash page. Note
that currently only some UIs (JSPUI/XMLUI) and in a very specific
configuration (discovery enabled as search provider, and the
SOLRBrowseDAOs is used for the Browse system) are fully rights aware.
This means that in different UIs or with different configurations
(legacy lucene search or DBMS browse) some metadata of a restricted
item could be exposed to unauthorized users. When you need to work with
UIs not fully rights aware, a workaround can be to use the "Private
Item" flag to make the item undiscoverable so that metadata will be not
exposed to unauthorized users."
We'd like to be sure that both bitstreams and metadata are completely
hidden while the item is under embargo.
Do you have any suggestions how to achieve this?
Best regards,
Franziska
Am 09.03.2016 um 16:35 schrieb Claudia Jürgen:
Dear Franziska
Two questions about "private items":
1. Can items with a private flag be found by bots, so they will appear
in Google Scholar, for instance?
They are accessible by bots via the direct hit on the splash page e.g.
http://mydspaceinstance/handle/yourprefix/nnnn
If you provide sitemaps for Google everything will be indexed. But
Google Scholar uses more than just the sitemaps to aggregate the
metadata.
If you do not use the handle system but another persisten identifier
e.g. DOI than anything will be available via DataCite and thus
distributed and made visible.
2. Are private items discoverable via OAI-PMH or other APIs?
They are not searchable and not in any lists, but accessible as single
records.
E.g. in OAI-PMH the should not appear in ListRecords/Idenfiers, but if
you know the identifier you cant retrieve them via GetRecord.
Hope this helps
Claudia Jürgen
We are using DSpace 5.4 with Mirage2.
Thank you and best regards,
Franziska
--
Claudia Juergen
Eldorado
Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund
Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
[email protected]
www.ub.tu-dortmund.de
Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich.
Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht
der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte
den Absender und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung
eines solchen Schriftstücks per Telefax erfolgen.
Important note: The information included in this e-mail is
confidential. It is solely intended for the recipient. If you are not
the intended recipient of this e-mail please contact the sender and
delete this message. Thank you. Without prejudice of e-mail
correspondence, our statements are only legally binding when they are
made in the conventional written form (with personal signature) or
when such documents are sent by fax.
--
You received this message because you are subscribed to the Google Groups "DSpace
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
