logging in or signing up metadata frames funnyside Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 50 Category: Product Traini.. License: All Rights Reserved Like it (0) Dislike it (0) Added: October 05, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Metadata Frameworks: Metadata Frameworks Fall 2003Metadata Frameworks: Metadata Frameworks ADN - for online/offline resources ** DLESE-IMS - for online resources Annotation - resource reviews, comments ** Collection - collection characteristics ** News-Opps - announcements **Design - Venetian Blind with chameleon namespaces Overall Challenge - Jan 2004 metadata workshop - whole ball of wax per Mike MayhewADN records: ADN records Web-based resources where resources are: Modules, lesson plans, activities, etc. Datasets (remote sensed, in-situ, model) Guides, text, visuals, imagery, etc. Strong data-typing with enforced required fields Has educational, technical, geospatial, temporal, relations, right, cataloger, creator, general categories Challenge - no direct meta generation supportDLESE-IMS records: DLESE-IMS records No data-typing; Required metadata not enforced Same ADN categories just less info in each category Geospatial and temporal are completely different than ADN (causes problem records for ADN) Has metadata generation support Annotation records: Annotation records Are the gatekeeper to the Reviewed Collection Are the gatekeeper as to whether library users can read or contribute reviews Can exist without ADN records Only 1 annotation type per record Annotations are in the record or a URL sends library user to a new site for the annotation Strong data-typing with enforced required fields Challenge - no direct meta generation supportCollection records (1): Collection records (1) Overall collection characteristics (title, descr.) Contains DPC collection key and metadata format (how to track collections through DPC) Indicates how a collection arrives at the DPC Is the collection OAI harvestable & the OAI info Is the collection generated at the DPC Is the collection emailed, ftp’ed or what Moderate data-typing with enforced required metadataCollection records (2): Collection records (2) Indicates if/how collections can be redistributed Info about item-level catalog record #’s Indicates super/sub/associated collections Can indicate ADL buckets for a collection Captures the additional info needed for NSDL Tracks accessioning and alignment with DLESE collection policies per requirement of the Collections Accessioning TaskforceCollection records (3): Collection records (3) Challenge - not sure if framework has all needed information Challenge - to produce valid records requires both DPC staff and a collection builder to create record Challenge - need to incorporate into other DLESE systems (DDS, histograms, OAI) Challenge - no metadata generation supportNews and Opps: News and Opps Allows for different announcement like grants, conf. wrkshps, interns. and start/stop, post/archive dates (non-standard) Has metadata generation support No vocabs or data typing except in GUI No longer valid records Mixes presentation with data (html, special chars issues) Challenge - per Karon, core services involvement; need better discovery and framework revamp?Dependencies and Versioning (1): Dependencies and Versioning (1) All frameworks are independent; even though some have same fields (good or bad???) All controlled vocabularies are individual schemas so that they can be plugged into any framework (namespaces are hidden) Collection, ADN & Anno are versioned in CVSDependencies and Versioning (2): Dependencies and Versioning (2) Collection, ADN & Anno records validate at schema locations on the metadata website through their overarching wrapper schema Metadata/adn-item/0.6.50/record.xsd Metadata/collection/0.1.01/collection.xsd Metadata/annotation/0.1.01/annotation.xsd New framework versions are issued when a tag is changed a vocabulary is changed (add/delete) or a new or modified field causes a structure changeDependencies and Versioning (3): Dependencies and Versioning (3) Challenge - the schemas enforce *lots* so they have lost some plug-n-play & the records are less flexible in coping with change Challenge - if give up some enforcement, records are more flexible when changes occur but data is more suspect (this philosophy needs to work closely with a UI because the UI would have to pick up some of the data enforcement)--- Probably not good for ADN but worth high consideration for News & Opps.Current Coll Formats (20 with 14 in DDS): Current Coll Formats (20 with 14 in DDS)Future Coll Formats (15) (Oct-Dec 2003): Future Coll Formats (15) (Oct-Dec 2003) You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
metadata frames funnyside Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 50 Category: Product Traini.. License: All Rights Reserved Like it (0) Dislike it (0) Added: October 05, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Metadata Frameworks: Metadata Frameworks Fall 2003Metadata Frameworks: Metadata Frameworks ADN - for online/offline resources ** DLESE-IMS - for online resources Annotation - resource reviews, comments ** Collection - collection characteristics ** News-Opps - announcements **Design - Venetian Blind with chameleon namespaces Overall Challenge - Jan 2004 metadata workshop - whole ball of wax per Mike MayhewADN records: ADN records Web-based resources where resources are: Modules, lesson plans, activities, etc. Datasets (remote sensed, in-situ, model) Guides, text, visuals, imagery, etc. Strong data-typing with enforced required fields Has educational, technical, geospatial, temporal, relations, right, cataloger, creator, general categories Challenge - no direct meta generation supportDLESE-IMS records: DLESE-IMS records No data-typing; Required metadata not enforced Same ADN categories just less info in each category Geospatial and temporal are completely different than ADN (causes problem records for ADN) Has metadata generation support Annotation records: Annotation records Are the gatekeeper to the Reviewed Collection Are the gatekeeper as to whether library users can read or contribute reviews Can exist without ADN records Only 1 annotation type per record Annotations are in the record or a URL sends library user to a new site for the annotation Strong data-typing with enforced required fields Challenge - no direct meta generation supportCollection records (1): Collection records (1) Overall collection characteristics (title, descr.) Contains DPC collection key and metadata format (how to track collections through DPC) Indicates how a collection arrives at the DPC Is the collection OAI harvestable & the OAI info Is the collection generated at the DPC Is the collection emailed, ftp’ed or what Moderate data-typing with enforced required metadataCollection records (2): Collection records (2) Indicates if/how collections can be redistributed Info about item-level catalog record #’s Indicates super/sub/associated collections Can indicate ADL buckets for a collection Captures the additional info needed for NSDL Tracks accessioning and alignment with DLESE collection policies per requirement of the Collections Accessioning TaskforceCollection records (3): Collection records (3) Challenge - not sure if framework has all needed information Challenge - to produce valid records requires both DPC staff and a collection builder to create record Challenge - need to incorporate into other DLESE systems (DDS, histograms, OAI) Challenge - no metadata generation supportNews and Opps: News and Opps Allows for different announcement like grants, conf. wrkshps, interns. and start/stop, post/archive dates (non-standard) Has metadata generation support No vocabs or data typing except in GUI No longer valid records Mixes presentation with data (html, special chars issues) Challenge - per Karon, core services involvement; need better discovery and framework revamp?Dependencies and Versioning (1): Dependencies and Versioning (1) All frameworks are independent; even though some have same fields (good or bad???) All controlled vocabularies are individual schemas so that they can be plugged into any framework (namespaces are hidden) Collection, ADN & Anno are versioned in CVSDependencies and Versioning (2): Dependencies and Versioning (2) Collection, ADN & Anno records validate at schema locations on the metadata website through their overarching wrapper schema Metadata/adn-item/0.6.50/record.xsd Metadata/collection/0.1.01/collection.xsd Metadata/annotation/0.1.01/annotation.xsd New framework versions are issued when a tag is changed a vocabulary is changed (add/delete) or a new or modified field causes a structure changeDependencies and Versioning (3): Dependencies and Versioning (3) Challenge - the schemas enforce *lots* so they have lost some plug-n-play & the records are less flexible in coping with change Challenge - if give up some enforcement, records are more flexible when changes occur but data is more suspect (this philosophy needs to work closely with a UI because the UI would have to pick up some of the data enforcement)--- Probably not good for ADN but worth high consideration for News & Opps.Current Coll Formats (20 with 14 in DDS): Current Coll Formats (20 with 14 in DDS)Future Coll Formats (15) (Oct-Dec 2003): Future Coll Formats (15) (Oct-Dec 2003)