What: Difference between revisions

From wiki.dpconline.org
Jump to navigation Jump to search
No edit summary
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 3: Line 3:
**What is the importance of the asset from the point of view of the institution?
**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?
**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.?
**What are the responsibilities? Who is the 'collection owner'? Who decides how it is catalogued, stored, etc.?
**Are there any rights issues associated with the content itself (eg privacy) or in the transfer (eg copyright)
**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?
**What resources do you have available? Is this entirely new, or an extension of something you are doing already in part or in whole?
Line 11: Line 11:
**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?
**Technical properties
**Technical properties
***What have you got: complexity/diversity, volume/growth
***(1) 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?
***(2) What is the carrier medium? Do you have large files that are difficult to process or move around your network?
***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?)
***(3) 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 tools are you using?)
***What is the expected usage? What is the long-term DP approach (just stablise / migrate / emulate)
***(4) What are the access conditions? What is the expected usage? How do you gather user requirements? How do you gather feedback?
**Provenance or audit trail properties
**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?
***(5) What do you need to control? What changes are you willing to accept? What do you need to track and what not?
***(6) What is the authenticity requirement?


*Solutions
*Solutions
**What are you proposing? What actions?
**What are you proposing? What actions?
**(1) What tools are do you need? Forensics? Characterisation? Etc.
**(2) Bit-level / carrier medium solutions: What is the refreshment cycle? Are you moving media?
**(3) Content solutions (just stabilise, migrate, emulate)
**(4) how much descriptive metadata do you need?
**(5) and (6) how much preservation metadata do you need?


***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
**further information
**characterisation
***characterisation
**case studies
***case studies
**content audit etc
***content audit etc

Latest revision as of 10:23, 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, stored, 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
      • (1) What have you got: complexity/diversity, volume/growth
      • (2) What is the carrier medium? Do you have large files that are difficult to process or move around your network?
      • (3) 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 tools are you using?)
      • (4) What are the access conditions? What is the expected usage? How do you gather user requirements? How do you gather feedback?
    • Provenance or audit trail properties
      • (5) What do you need to control? What changes are you willing to accept? What do you need to track and what not?
      • (6) What is the authenticity requirement?
  • Solutions
    • What are you proposing? What actions?
    • (1) What tools are do you need? Forensics? Characterisation? Etc.
    • (2) Bit-level / carrier medium solutions: What is the refreshment cycle? Are you moving media?
    • (3) Content solutions (just stabilise, migrate, emulate)
    • (4) how much descriptive metadata do you need?
    • (5) and (6) how much preservation metadata do you need?


  • further information
    • characterisation
    • case studies
    • content audit etc