...
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
- Conceptual document and needs assessment
- PREMIS priorities from bare minimum to perfection
- business cases to prioritize preservation and PREMIS
Implementation
Gregory Jansen described this as "SWORD for a PREMIS event." In other words, we need to build services that talk to your PREMIS datastream, regardless of how you encode the data stream. The fact that many people end up my using the same encoding will be valuable but not necessary.
Some of the tools we can build will be completely project independent. For example, firing off an audit trail that a virus checker ran is independent of whether or not you are using Fedora, DSpace, or what have you.How do we make business cases to prioritize preservation and PREMIS?
Participants
Please add yourself!
...