...
- How can we improve the stakeholder engagement/feedback process?
- Verification tool
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2284 - Requirements (discussion)
- Verify same number of resources on disk as in fcrepo
- Verify same number of resources in fcrepo as on disk
- Verify same checksum for binaries
- Verify same triples for containers
- Record which resources have been verified
- Others?
- Verify fcrepo to fcrepo
- Verify disk to disk
- Use generated config file as sole input
- Overview of Phase 2 requirements
- Support import from and export to a TBD list of external systems
- APTrust
- Archivematica
- MetaArchive
- Support transacting in BagIt bags
- Support export of resource and its "members" based on a user-provided membership predicate
- Single resource bags
- The structure and scope of accepted and produced BagIt bags must be configurable
- Clarification: structure relates to required and optional tagfiles in the bag
- Clarification: scope relates to contents of the bag, e.g. single object or object and all members based on specific membership predicate
- Overview of existing Phase 2 tickets
- Support import from and export to a TBD list of external systems
- Sprinters
- Developers
- Testing and Validation
- Documentation
- ...
Minutes
- Improving Stakeholder Feedback
- Reach out to Fedora Leaders to ask them to make participation a priority.
- Circulate the call for feedback more widely (currently went only to the two Fedora lists, but could go to Islandora and Hydra communities as well).
- It is OK to reach out directly to folks who have previously self-identified as stakeholders but who have not yet responded.
- Perhaps setting up a framework in which more help was available for those wishing to test and give feedback would encourage participation from folks who are otherwise hesitant about their own ability to contribute.