Enable and Test DRS server

[bwalsh]

Use Case

As an ACED user, when I am using DRS, it would be useful to have DRS functionality enabled in our servers.

Background

see https://github.com/uc-cdis/indexd#standards-and-governance

michael_fitz
aced-idp

• No, you do not need a separate prefix for your different environments for the same commons. You would only need to do that if you want to test it like that. Usually that doesn’t make sense as you only have data that matters in prod and the data that exists in your other environments don’t need a prefix. In most cases a prefix for a DRS server is not registered to dataguids.org. Most people use identifiers.org or n2t.net
  With respect to your more general question - there’s really not much difference between an indexd record with a prefix and without a prefix. The only difference is that you can use a central resolver to find where the prefix is pointing to. The way you can test this is after registering your prefix somewhere you can then resolve it and try to download the file.

You can set the default prefix in indexd here in the indexd config https://github.com/uc-cdis/indexd/blob/master/indexd/default_settings.py#L23

GA4GH recommends identifiers.org, but this is actually new so not all DRS clients may recognize this yet. CTDS uses dataguids.org
Agreed, but the process isnt too bad to register it in identifiers.org. I've done it for a couple of DRS servers here at UChicago for both resolvers and am happy to help with that process.
should we have a prefix for each of our environments? (i.e. staging, qa, prod)
I personally dont think you dont need to. Im guessing qa will mostly have test data. We've usually just registered prod envs for the resolvers. The other environments can have the same prefixes but it just wouldn't be registered.

https://registry.identifiers.org/resourceregistrationrequest

Slack conversation: https://ohsucomputationalbio.slack.com/archives/C043HPV0VMY/p1685116572286549

[matthewpeterkort]

Clarifying- we need to do a prefix request not a resource request???
ex: https://registry.identifiers.org/prefixregistrationrequest

[bwalsh]

I believe that is correct.

[matthewpeterkort]

Addressed in Slack: https://ohsucomputationalbio.slack.com/archives/C04NBBLTY12/p1708717803612439

[bwalsh]

Tasks:

• Complete registration @kellrott
• Complete Development configurations (fence, etc.) @matthewpeterkort
  • Develop test plan
  • Write automated tests
• Complete migration plan for staging, production @matthewpeterkort
  • Deploy to staging, production

[matthewpeterkort]

Draft form entry for: https://registry.identifiers.org/prefixregistrationrequest

647)