-
Notifications
You must be signed in to change notification settings - Fork 7
Home
The SDR3 Management API and Persistence Skeleton, aka TACO, is foundational and extensible work for the evolution of our current digital object repository. It is the basis for new & existing components, addressing core problematic technology (namely, Fedora 3) while serving user requirements for flexible and consistent ingest and data models.
The DLSS TACO Prototype is a core part of our SDR3 Evolution plan. You can read more about the SDR3 Evolution plan on it's DLSS Consul Page. We would particularly point you to our SDR3 Evolution Roadmap for understanding the context on this TACO Prototype work.
The TACO Prototype work cycle is our first SDR3 work cycle. We have a few goals for this TACO Prototype work:
| Functional Goals | Technological Goals | Process Goals |
|---|---|---|
| Deposit resources (binaries & metadata) into the repository core via RESTful API. | Drive forward DLSS repository API specifications, implementations, & practices. | Work towards new core with something visible to limited stakeholders to make it real-er. |
| Retrieve deposited resources from the repository core via RESTful API. | Test & select implementation options for our current design. | Get feedback on design, check for roadblocks. |
| Persist resources in canonical datastores. | Vet our data models & metadata profiles. | Keep to high-level, extensible functional blocks. |
| Perform skeletal resource processing for repository needs (i.e. workflows). | Test feasibility of possible technologies: Hyrax integration points; Test throughput / scalability; SDR2 & SDR3 analytics; Inform serverless / cloud practices. | Showcase internal / lower stack rewrites needed for moving middle and end-user codebases forward. |
See a detailed slidedeck with information on TACO prototype technology evaluation & selection here.
We are documenting where we've started evaluation of both the TACO Design (coming from SDR3 Design Group) and feasibility of new technologies for the requirements outlined in this prototype. Use the sidebar for links to our documentation.
TACO Design Documents, Meeting Notes, etc. can be found in our TACO Prototype Google Drive folder.
The TACO Workcycle is driven by the design decisions made during the SDR3 design cycle.
- TACO API & Service Design
- Development Guide
- TACO Internal Steps
- Identifier schema
- Data Modeling & MAPs
- Data Expectations of TACO
- Auth & Permissions
- Benchmarking Goals & Scenarios
- Workflows & Robots Replacement Analysis