Project Overview
Purpose
The purpose of this document is to create a common understanding between all partners involved in the development process to ensure that the right system/tool is being built.
Goals of this document
offers the reader an understanding of the development goals
presents the system architecture and description
makes the reader aware what is being build
will be updated regularly, but is written with an understanding at this time, even if its not correct
the document will include feedback and corrections from the development community
High Level Overview
There are many research data repositories in use within higher education today. Oftentimes, researchers will have a need and/or desire to work in multiple data repositories concurrently.
This desire can be frustrated as disparate systems are often not able to directly share resources; or if able to share resources, do so in less than ideal fashions.
The overall goal of PresQT
The development team is tasked to deliver tools and services that allow enhancement of and action on metadata related to keywords, provenance, quality, and fixity and ensure that such enhancements and actions are also portable/queryable/executable across repository systems
For extended development teams at partner organizations their jobs are to support interoperability testing (help conceive of and build the tests, help do the testing) of our tools and features against the target systems they develop or use. For the testing only partners at the collaborating organizations they may provide testing or testers on their own systems or to do testing on our's.
Potential Target Systems
CERN
Fedora
S3
Development Roadmap
Infrastructure Setup using Docker
Setup continues integration tool
General use cases. Upload/download of objects from one repo to another or to local environment.
Development of fixity web service
Development of preservation quality web service
Development of keyword assignment web service
Testing
Integration with partner repo's
The roadmap can be found here.
Issues for Investigation
It seems like many of the systems that we are going to interact with have themselves already provided the ability to save data to various back-ends. That will be a point of user confusion.
It seems like some of these partners may actually embed the software that we develop inside their applications.
Clarify how authentication is being handled when we provide a docker image to the community for testing via a web accessible system with API endpoints where OSF and currateND is being used as first use case.
Last updated