Change visibility of Data from: A Glimpse through Time and Space: Visualizing Social Memory...(2018)

[hjsyoo]

Descriptive summary

De-index all pages in the Catalhoyuk Glimpse (v1) collection: https://library.ucsd.edu/dc/collection/bb3485072m, so they stop turning up in a search (DAMS or Google).

• 1 collection page
• 8 object pages

The pages should continue to be accessible by URL.

Related work

• https://ucsdlibrary.atlassian.net/browse/DI-266
• https://docs.google.com/spreadsheets/d/1M96UIFczSFOixH-qdqMKHeuIkY65NWAhRp4QixUKqok/edit#gid=1723491446

[gamontoya]

@mcritchlow @lsitu What does this entail, exactly (Solr, Google?)?

[lsitu]

@gamontoya @hjsyoo I think we've never done that to de-index any records in dams but change the visibility of a collection to curator only access. Is it what we need to do? And I have to clarify that we have no control over the objects from showing up on search engines once the objects are caching there. @mcritchlow Do you have any ideas on it?

[arwenhutt]

@lsitu @gamontoya @mcritchlow hi all, @hjsyoo will need to confirm, but I believe what is being requested is to suppress discovery for these items (like the open topography collection/items).

If that's the case, then we (DOMM) may be able to do this by editing the records and adding the suppress public discovery note, which should then trigger the appropriate access controls.

Let us know if that sounds right, thanks!

[arwenhutt]

@lsitu @gamontoya @mcritchlow

I confirmed with @hjsyoo on slack that these should be changed to suppress discovery, and have updated the 8 objects with the other rights note:

   <dams:otherRights>
      <dams:OtherRights>
        <dams:restriction>
          <dams:Restriction>
            <dams:type>suppressDiscovery</dams:type>
          </dams:Restriction>
        </dams:restriction>
        <dams:otherRightsNote>Suppress public discovery</dams:otherRightsNote>
      </dams:OtherRights>
    </dams:otherRights>

They are all working as expected (i.e. not showing up in DAMS PAS search (when not logged in as curator), but visible via direct ark or doi link.

I also updated the CLR adding:

suppressDiscovery Which did not function as expected, instead it made the CLR unavailable without being logged in.

~I tried a few different things, and did get the desired functionality by removing the <dams:visibility> property and adding the <dams:otherRights> note above to the CLR. But this is a temporary work around, and we'll want to fix the suppressDiscovery functionality as part of the access control work.~

[hjsyoo]

Thanks @arwenhutt ! I was using the wrong vocabulary. The objects are behaving as expected now, but aside from the bug issue, can we have the collection page be publicly visible (without changing the suppressDiscovery status of the objects)? If the only two possible states for the collection page are [public access & discoverable] vs. [curator only & suppressDiscovery], then the former state is preferable. Ultimately, I would like all objects and collection page to be [public access and suppressDiscovery].

Note - As non-curator, I currently get the Forbidden page when trying to access the collection page via DOI URL.

[arwenhutt]

@lsitu @gamontoya @mcritchlow It looks like I was wrong about the CLR functioning! I've edited my comment above to correct.

So it looks like we still have a bug with the CLR suppress discovery functionality.

[gamontoya]

@arwenhutt Your discovery sounds like a separate issue. Can you create a new ticket for this bug?

[arwenhutt]

@gamontoya sure, damspas or damsmanager?

[lsitu]

@arwenhutt I think we can create the ticket on damsrepo to fix the behavior for CLR suppressDiscovery.

[arwenhutt]

@lsitu @gamontoya @hjsyoo I created a new ticket in damsrepo: https://github.com/ucsdlib/damsrepo/issues/99 It looks like I don't have permissions to add people/tags etc. so it doesn't have anything except the title and body, so it doesn't have anyone or any tags.

[lsitu]

@arwenhutt Thanks. I'll look into it.

[gamontoya]

@lsitu @arwenhutt What's the status on this ticket. Is it waiting for someone/something?

[lsitu]

@gamontoya I think should be done through ticket https://github.com/ucsdlib/damsrepo/issues/99 (PR https://github.com/ucsdlib/damsrepo/pull/100).

[hjsyoo]

Has the fix been deployed? Are we now able to suppress discovery of this collection page?

[lsitu]

@hjsyoo Yes. It was deployed to prod last month in Oct. 15.

[hjsyoo]

@arwenhutt Looks like we can give this a whirl!

[hjsyoo]

@arwenhutt I think we're okay to change this collection page to discovery-suppressed. Can you give it a try? If it works, then I'll write up some text to be added to the Description, so that even if the View Collection Items button doesn't pull up anything for non-Curators, there will at least be a series of DOIs that link to the 8 objects within the collection.

[arwenhutt]

@hjsyoo Done - but double check! I searched for "Data from: A Glimpse through Time and Space" (not logged in, private firefox window) and it returns 9 things (8 objects, 1 clr) with the 2019 citation date.

A little more information for documentation's sake: The visibility metadata had been updated before, but then when we were troubleshooting why the view objects in collection button didn't work, I tried re-releasing the collection. I think that may have reset the visibility value (Slack conversation link) - but let's keep an eye on it.

[hjsyoo]

Awesome, thank you, it works for me, too with 9 returned things. So now, in https://library.ucsd.edu/dc/collection/bb3485072m, what do you think of adding this text to the Description, after the first short paragraph and before "This collection includes a set of 3-D models..."?

The 8 items in this collection can be accessed through the following Digital Object Identifier links:

https://doi.org/10.6075/J0WD3XWM https://doi.org/10.6075/J0G44NMM https://doi.org/10.6075/J0BC3WWW https://doi.org/10.6075/J02Z13VJ https://doi.org/10.6075/J0057D8C https://doi.org/10.6075/J0VD6WT4 https://doi.org/10.6075/J0QN6536 https://doi.org/10.6075/J0KW5DCG

[arwenhutt]

@hjsyoo That sounds like a good option. I've added it to the clr https://library.ucsd.edu/dc/collection/bb3485072m

[hjsyoo]

Thanks, @arwenhutt !