Metadata Only Repository & Allocation #1482
JoshuaSBrown
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem We Want to Solve
We want to figure out how to represent a repo in ArangoDb when someone is using Metadata Mode. The Repo and User documents are nodes in the database, the allocation connects the two.
Why not have a separate allocation per repository per project?
We don't need multiple repo's to support metadata only repository because there is no physical location for the raw data files.
We assume that you only need 1 repository when in Metadata mode
Describe the Solution You'd Like
There are 2 ways to create an alloc
Additional context
How a repo looks in Arango
Arango Queries for setting up Repo + Alloc
Data Model
https://confluence.ccs.ornl.gov/pages/viewpage.action?pageId=344163314&spaceKey=DATAFED&title=STRUCTURAL%2B-%2BData%2BModel%2B1
For a Metadata only repo, only need
For a metadata only repo, only need
Files of importance are:
support.js (assignRepo function)
support.js (verifyRepo function)
repo_router.js ( .post("/create"))
core/database/foxx/api/support.js:178
A type associated with a repository
Globus
Metdata_only
maybe you need to have an alloc? A specific alloc
If there's a repo of one type, we might need an alloc of the same type, 1:1. Might be lower-risk to leave the API as is and provide empty or default values in specific fields
Beta Was this translation helpful? Give feedback.
All reactions