ucsdlib / damspas

UC San Diego DAMS Hydra Head
Other
7 stars 5 forks source link

Perform audit of bb (prod) ARKs on staging #347

Closed gamontoya closed 7 years ago

gamontoya commented 7 years ago

Descriptive summary

An audit needs for assigned ARKs on staging; specifically looking for any bb-ARKs used on staging.

Rationale

Ryan is working on a collection on staging that has a bb-ARK (https://librarytest.ucsd.edu/dc/collection/bb8158593z). It should be using a bd-ARK and the question seems to be, "How did this happen?"

VivianChu commented 7 years ago

@gamontoya - I confirmed with Ron that the properties file for damsManager in staging is configured to use bd ark minter. I also created a test collection record in staging and it used a bd ark. https://librarytest.ucsd.edu/dc/collection/bd8720339f The collection record above (https://librarytest.ucsd.edu/dc/collection/bb8158593z) was also in production https://library.ucsd.edu/dc/collection/bb8158593z I think this record was a result of a sync to get prod data into staging. The last time we did the data sync was on July 2017 https://lib-jira.ucsd.edu:8443/browse/IO-47 In staging , 128 collection records have bb ark and 54 collection records have bd ark. 110927 objects have bb ark and 4066 have bd ark.

gamontoya commented 7 years ago

@mcritchlow Does this satisfy your concern(s)?

mcritchlow commented 7 years ago

Yeah I think so. I'm sure Vivian is right and this was the result of a sync. I think this is just an artifact of what the staging environment has become.. Thanks for digging into this, Vivian!

On Fri, Oct 6, 2017, 4:46 PM Gabriela A. Montoya notifications@github.com wrote:

@mcritchlow https://github.com/mcritchlow Does this satisfy your concern(s)?

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/ucsdlib/damspas/issues/347#issuecomment-334894266, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEHsgURvn2ifKIE-FyxkRCcaG6alLJGks5sprvggaJpZM4PW3ue .