1. Group description
This group will address the real need for a standard way to describe and store and act upon PREMIS in Fedora or DSpace object. We'll start with concepts, and then move when appropriate to implementation forks.
Goals
This first pass of the goals came out of the PREMIS birds of a feather at open repositories 2010.
Conceptual document and needs assessment
Priorities
What do we mean when we say we want standard ways of using PREMIS? For this, we should get both Fedora and DSpace users to contribute use cases. These aren't just use cases of currently in use PREMIS solutions, but what people think they need PREMIS for.
We agree that there are multiple stages of what can be considered preservation-worthy PREMIS. As a community, we need to come to consensus at what is the bare minimum of enough. Let's do that here: PREMIS priorities from bare minimum to perfection.
- Bare minimum. If you don't track these things, your peers will not consider you to be doing preservation.
- Happy medium. What are the steps? These are the goals for institutions not doing the bare minimum. How do you prioritize which ones to select from this list?
- A perfect world. The goal toward which we should be reaching. Probably, TRAC. (Which elements of TRAC map tidily to a PREMIS trail?)
Business cases
How do we make business cases to prioritize preservation and PREMIS?
Participants
Please add yourself!
- Deborah Kaplan, Tufts University
- Gregory Jansen, University of North Carolina at Chapel Hill
- Ron Jantz, Rutgers University
Use cases
Not just for institutions using PREMIS now. What needs do you forsee for PREMIS?
Working documents:
- Requirements for defining a PREMIS standard for Fedora
- Descriptions of projects currently in place or in planning
Links:
