Talk:Understand collection: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
* The approaches section may be too technical for the business case stage- depends on why you are making the business case/who you are making it for | * The approaches section may be too technical for the business case stage- depends on why you are making the business case/who you are making it for | ||
* Need to prioritise intellectual content over bit level preservation | * Need to prioritise intellectual content over bit level preservation | ||
* Guidance and policies on accepting digital assets could be reworded as 'collections development policies' | |||
* Is the section on fixity and checksums about understanding the state of the collection currently? |
Latest revision as of 16:39, 30 July 2013
- What is meant by content assessment? Need to understand types of content as well as file formats e.g. maps to identify preservation intent
- End users should also be considered: what sort of access is needed?
- The approaches section may be too technical for the business case stage- depends on why you are making the business case/who you are making it for
- Need to prioritise intellectual content over bit level preservation
- Guidance and policies on accepting digital assets could be reworded as 'collections development policies'
- Is the section on fixity and checksums about understanding the state of the collection currently?