simonsobs / simonsobs/librarian
Allow for manifest ingestion as a 'remote instance'
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- Avg merge
- 10d 21h
- Merged PRs (30d)
- 1
Description
We could, for catchup, simply send over a manifest of a downstream librarian's stores to an upstream librarian, and have them entered as remote instances of those files (including checksum checking).
So a procedure would look like this:
- Librarian A dumps a manifest_A
- Files and manifest_A copied
- Files ingested into Librarian B using manifest_A
- Librarian B dumps manifest_B
- Manifest_B is copied to Librarian A host
- Librarian A 'ingests' manifest_B as a remote instance table for Librarian B
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by locating the existing manifest handling and remote-instance table paths, then determine how the described dump, copy, ingestion, and checksum steps fit together; done means the procedure works in both directions with verified file instances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100