It seems we have a healthy discussion about Œdark copy¹ and this is good.
So the culprit was not the software itself, but the documentation as to how this could be configured. I guess, I might be back in the Editor Gardner¹s seat very soon. Thanks to Tim, Helix, and Andrea for their valuable insights in assisting me and my endeavors. ‹Jeff Jeffrey Trimble Associate Director & Head of Information Services William F. Maag Library Youngstown State University 330.941.2483 (Office) [email protected] http://www.maag.ysu.edu http://digital.maag.ysu.edu "For he is the Kwisatz Haderach..." On 1/21/14, 12:48 PM, "Tim Donohue" <[email protected]> wrote: >As a followup to my own email: It looks like it *is* documented how to >disable this Access Rights Awareness feature. It's just not so easy to >find the docs on it. > >Here's the details: >https://wiki.duraspace.org/display/DSDOC4x/Discovery#Discovery-Accessitemb >asedresults > >So, we probably just need to make this a little easier to find. It took >some searching in the docs before I realized it actually is there. > >I agree with Andrea Bollini here though. I personally like this feature. >I can understand there may be use cases where it's not desirable. But, >by default, I'd prefer we *hide* metadata for access-restricted Items, >rather than making it publicly available/searchable. > >- Tim > >On 1/21/2014 11:38 AM, Tim Donohue wrote: >> We should better document how to turn off/on Access Rights Awareness. I >> *believe* it's a matter of commenting out this setting (but it's unclear >> to me as well, and I don't know enough about this feature): >> >> >>https://github.com/DSpace/DSpace/blob/master/dspace/config/spring/api/dis >>covery.xml#L25 >> >> >> To clarify here, different institutions definitely have different use >> cases for DSpace, and often based on the use case they may have >> differing opinions of this feature. >> >> There are institutions who are adamantly in favor of Access Rights >> Awareness (as they do NOT want Google/Google Scholar to index items >> whose metadata is private -- e.g. some of those items may be private >> records or embargoed and they do not wish them to be discoverable at >> all). There are also insitutions (which Jeff & helix84 are members) who >> are adamantly against Access Rights Awareness (as they want Google to >> index all metadata, whether that item is private or public or >>embargoed). >> >> So, Access Rights Awareness is probably something we need to better >> document & also better document how to disable it if you favor exposing >> *all* metadata as publicly searchable/browsable. >> >> - Tim >> >> On 1/21/2014 11:12 AM, helix84 wrote: >>> Hi Jeff, >>> >>> here's how you can turn Access Rights Awareness off: >>> >>> >>>https://jira.duraspace.org/browse/DS-1229?focusedCommentId=25563&page=co >>>m.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2 >>>5563 >>> >>> >>> I also find it unfortunate that it's on by default. >>> >>> >>> Regards, >>> ~~helix84 >>> >>> Compulsory reading: DSpace Mailing List Etiquette >>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >>> > ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
