Difference between revisions of "CURATEcamp SAA 2012 Discussion Ideas"
From CURATEcamp
Line 6: | Line 6: | ||
* '''Embedded Metadata''' (Cristela Garcia-Spitz): Digital objects are now living on the web, often with little or no associated metadata within the content file. Sometimes it is only a filename that travels with the object. What can be done to embedded the rich metadata (title, date, institution, rights, etc.) into the object (image, text, audiovisual, data sets)? | * '''Embedded Metadata''' (Cristela Garcia-Spitz): Digital objects are now living on the web, often with little or no associated metadata within the content file. Sometimes it is only a filename that travels with the object. What can be done to embedded the rich metadata (title, date, institution, rights, etc.) into the object (image, text, audiovisual, data sets)? | ||
+ | |||
+ | * '''Legacy File Identification/Appraisal''' (Matthew McKinley): My topic comes in two parts: 1. Files older than 8-10 years are often initially inaccessible for a variety of reasons--outdated/unsupported creating software, unreliable extensions/naming, lack of technical metadata--and thus are often not identified or mis-identified by identification/characterization software such as JHOVE, DROID, Tikka etc. What can be done to improve their identification? 2. Once identified, is there a way for these files to be viewed/appraised/searched by "non-techie" archivists without proprietary software (FTK) or complex CLI manipulation (AFFLib)? |
Revision as of 23:18, 17 July 2012
Feel free to use this space to share ideas for discussion at CURATEcamp 2011.
Topic you are interested in (Your name): A sentence or three about your topic.
- Embedded Metadata (Cristela Garcia-Spitz): Digital objects are now living on the web, often with little or no associated metadata within the content file. Sometimes it is only a filename that travels with the object. What can be done to embedded the rich metadata (title, date, institution, rights, etc.) into the object (image, text, audiovisual, data sets)?
- Legacy File Identification/Appraisal (Matthew McKinley): My topic comes in two parts: 1. Files older than 8-10 years are often initially inaccessible for a variety of reasons--outdated/unsupported creating software, unreliable extensions/naming, lack of technical metadata--and thus are often not identified or mis-identified by identification/characterization software such as JHOVE, DROID, Tikka etc. What can be done to improve their identification? 2. Once identified, is there a way for these files to be viewed/appraised/searched by "non-techie" archivists without proprietary software (FTK) or complex CLI manipulation (AFFLib)?