Closed kjgarza closed 2 years ago
Thanks @jrhoads , it looks great. there are a few details but i guess they just need clarification. I include them here and in usersnap.
Fixed feature 5.2
Re: Feature 3.
In staging, the client information does not contain the re3dataId. In production, it does. In this particular case it will work out just fine in production.
It is conceivable that a client repository in production does not have a re3dataId set even when when one exists in re3Data. In that case they would show up as separate entries in the repository search in commons.
Scenario 2.2 and 2.3 I am not sure how re3data runs it's queries on their end. The current deployment to staging shows numbers similar to repository finder for both of the filters.
Validation's complete.
@jrhoads will prepare a separate PR for addressing https://github.com/datacite/tasks/issues/97.
:fireworks: Well done @jrhoads this is a wrap! Could you fill this small retrospective survey to share your experience during this release https://forms.gle/tUrjLfRrhCB7uQg39. :sparkles:
DOD: Repository search in DataCite Commons
Development Checklist
Product Engineering Checklist
Feature: Redirect Search/Repository Finder to CommonsEngagement Checklist