What: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
*Technical questions | *Technical questions | ||
**What do you need to know - how much detail? Know what you don't need to know. What is enough information? | **What do you need to know - how much detail? Know what you don't need to know. What is enough information? | ||
**What have you got: complexity/diversity, volume/growth | **Technical properties | ||
**Provenance or audit trail | ***What have you got: complexity/diversity, volume/growth | ||
***What is the carrier medium? What is the refreshment cycle? What are you going to do about it? | |||
***What formats do you have? Are these problematic? (e.g. can you render the format? do files render correctly? what level of QA does the collection need - e.g. file by file? - do you have the resources available for the workflow?) | |||
***What long-term DP approach are you proposing? Do you need to propose an approach? Can you just stabilise? Or do you need to think about migration/emulation. | |||
**Provenance or audit trail properties | |||
***What do you need to control? What changes are you willing to accept? What do you need to track and what not? | ***What do you need to control? What changes are you willing to accept? What do you need to track and what not? | ||
*Solutions | |||
**What are you proposing? What actions? | |||
***Once we know who we need to communicate with we then can start looking at what we've got ... We can describe the assets that we have. | ***Once we know who we need to communicate with we then can start looking at what we've got ... We can describe the assets that we have. |
Revision as of 10:09, 31 July 2013
- Curation questions
- Where does the stuff come from? How will be reused and by whom? What are their requirements?
- What is the importance of the asset from the point of view of the institution?
- Do you need to provide guidance or support, to the depositor or to the user?
- What are the responsibilities? Who is the 'collection owner'? Who decides how it is catalogued, etc.?
- Are there any rights issues associated with the content itself (eg privacy) or in the transfer (eg copyright)
- What resources do you have available? Is this entirely new, or an extension of something you are doing already in part or in whole?
- Technical questions
- What do you need to know - how much detail? Know what you don't need to know. What is enough information?
- Technical properties
- What have you got: complexity/diversity, volume/growth
- What is the carrier medium? What is the refreshment cycle? What are you going to do about it?
- What formats do you have? Are these problematic? (e.g. can you render the format? do files render correctly? what level of QA does the collection need - e.g. file by file? - do you have the resources available for the workflow?)
- What long-term DP approach are you proposing? Do you need to propose an approach? Can you just stabilise? Or do you need to think about migration/emulation.
- Provenance or audit trail properties
- What do you need to control? What changes are you willing to accept? What do you need to track and what not?
- Solutions
- What are you proposing? What actions?
- Once we know who we need to communicate with we then can start looking at what we've got ... We can describe the assets that we have.
- What have you got - complexity, volume
- what do you need to do?
- Assess your digital collections
- Identify risks and challenges
- Identify solutions
- further information
- characterisation
- case studies
- content audit etc
- further information