NDSA:Content Registry Fields: Difference between revisions
Added fields for proposed content registry. |
mNo edit summary |
||
| Line 1: | Line 1: | ||
After reviewing our survey to the NDSA Alliance, the Content Registry Action Team decided to try an build a Registry based on the Recollection tool from the Library of Congress. As of July 5, 2011, we were considering requiring the following fields: | After reviewing our survey to the NDSA Alliance, the Content Registry Action Team decided to try an build a Registry based on the Recollection tool from the Library of Congress. As of July 5, 2011, we were considering requiring the following fields: | ||
Subject | *Subject | ||
Name of Specific Collection | *Name of Specific Collection | ||
URL | *URL | ||
Collection Availability (i.e. Public on web, public within building, no access) | *Collection Availability (i.e. Public on web, public within building, no access) | ||
Collection Start Date | *Collection Start Date | ||
Collection End Date | *Collection End Date | ||
Collection Location (Optional - What geographic locations does this collection pertain to?) | *Collection Location (Optional - What geographic locations does this collection pertain to?) | ||
Content Type | *Content Type (born digital, digitized from tangible materials) | ||
Description | *Description | ||
Digital Preservation Fields (Based on http://www.ala.org/ala/mgrps/divs/alcts/resources/preserv/defdigpres0408.cfm), a "Y" in field indicates that all aspects of this Digital Preservation area have been met. This would be self reported by the partner institution | Digital Preservation Fields (Based on http://www.ala.org/ala/mgrps/divs/alcts/resources/preserv/defdigpres0408.cfm), a "Y" in field indicates that all aspects of this Digital Preservation area have been met. This would be self reported by the partner institution | ||
DP in Content Creation – y/n | *DP in Content Creation – y/n | ||
DP in Content integrity – y/n | *DP in Content integrity – y/n | ||
DP in Content maintenance – y/n | *DP in Content maintenance – y/n | ||
Institution Name | *Institution Name | ||
Collection Contact (e-mail and phone) | *Collection Contact (e-mail and phone) | ||
Currently we envision partner institutions filling out an Excel spreadsheet with the information above and sending it to a registry maintainer yet to be determined. | Currently we envision partner institutions filling out an Excel spreadsheet with the information above and sending it to a registry maintainer yet to be determined. | ||
Revision as of 11:48, 6 July 2011
After reviewing our survey to the NDSA Alliance, the Content Registry Action Team decided to try an build a Registry based on the Recollection tool from the Library of Congress. As of July 5, 2011, we were considering requiring the following fields:
- Subject
- Name of Specific Collection
- URL
- Collection Availability (i.e. Public on web, public within building, no access)
- Collection Start Date
- Collection End Date
- Collection Location (Optional - What geographic locations does this collection pertain to?)
- Content Type (born digital, digitized from tangible materials)
- Description
Digital Preservation Fields (Based on http://www.ala.org/ala/mgrps/divs/alcts/resources/preserv/defdigpres0408.cfm), a "Y" in field indicates that all aspects of this Digital Preservation area have been met. This would be self reported by the partner institution
- DP in Content Creation – y/n
- DP in Content integrity – y/n
- DP in Content maintenance – y/n
- Institution Name
- Collection Contact (e-mail and phone)
Currently we envision partner institutions filling out an Excel spreadsheet with the information above and sending it to a registry maintainer yet to be determined.
Please comment on this page or send e-mail to daniel.cornwall@alaska.gov. In addition to feedback on the fields (add, subtract or delete), we'd like comment on how we can make this as easy as possible for the partner institutions. We'll take feedback until July 22nd, then send out a an alliancewide survey on July 25th or July 26th.