Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorporate references to legacy datasets; consolidate doc #53

Closed
JoanneBogart opened this issue Aug 18, 2023 · 1 comment
Closed

Incorporate references to legacy datasets; consolidate doc #53

JoanneBogart opened this issue Aug 18, 2023 · 1 comment

Comments

@JoanneBogart
Copy link
Collaborator

JoanneBogart commented Aug 18, 2023

Come up with a way to reference datasets not necessarily registered in the system.
Look into existing Confluence page(s) concerning production datasets
Should/can production have a separate root from non-production?

@JoanneBogart
Copy link
Collaborator Author

Closing this issue because the points raised are being discussed elsewhere.
For the first, see issue #104 and associated PR #112
The production db will have a separate root dir. For other dbs, their production subdir will typically be a sym link to the production (or possibly differently named) subdirectory of the production root dir. See some discussion in issue #106.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant