• Embed Doc
  • Copy Link
  • Readcast
  • Collections
  • CommentGo Back
Download
 
Metadata requirements for EngSC OER project
Lisa Rogers <L.J.Rogers@hw.ac.uk> & Phil Barker <philb@icbl.hw.ac.uk>.ICBL, MACS, Heriot Watt University <http://www.icbl.hw.ac.uk/>
Created: 03-Oct-2009Because Phil said "It would be useful first to define what information about a resourceyou think should be provided, why, for whom, and in what format."
Who:
includes project funders (HEFCE + JISC and Academy as their agents), project partner contributing resource, project manager, end users (teachers and students),aggregators—that is people who wish to build services on top of the collection.
Why:
includes resource management, selection and use as well as discovery throughGoogle or otherwise, etc. etc.
Format:
includes free text for humans to read (which is incidentally what Googleworks from) and encoded text for machine operations (e.g. XML, RSS, HTMLmetatags, microformats, metadata embedded in other formats or held in the databaseof whatever content management system lies behind the host we are using).It is important to keep the requirements manageable, and hence speculative uses(where use = who + why) have been avoided. For each use we should be able to pointto an actual instantiation that is at least planned, if not under development or implemented.This work is licensed under aCreative Commons Attribution 2.5 License.
 
Metadata requirements for EngSC OER projectPhil Barker & Lisa J Rogers Heriot-Watt University
CharacteristicFor WhomWhy?FormatNotes
TitleEnd UserAid resource discoveryand selectionHuman readable. In resource, as title page and as running header; or onresource display page. Formatted asheading / title or running header. Needs to convey maximum information inminimum space, e.g. subject + levelformula of "Perl for beginners"Host platforms must allow title to bespecified on upload and handle display onresource page and metadata in feeds.Do any host systems extract embeddedmetadata other than Flickr from images?In structured markup <title>, <h1>,suitable word style / format.May be worth adding to EXIFmetadata of images.ContributorEasy reference, to allowrapid identification andlocation of knownresource.If search is via Google then format asabove.If search is via API then must be inhost's content management metadata.Proj Mngr AggregatorsDisplay of availableresourcesRSS/ATOM item-level title<item><title>DescriptionEnd UserSearch &SelectionHuman readable. In resource asabstract, or on resource display page.Should be short and key-word intensive;including content subject and level. page 2 of 8
 
Metadata requirements for EngSC OER projectPhil Barker & Lisa J Rogers Heriot-Watt UniversityHost platforms must allow description to be specified on upload and handle displayon resource page and metadata in feeds.In structured markup <metadescription = ""> if that can be doneautomatically.AggregatorsDisplay to usersIn RSS/ATOM item-level description<item><description>Provenance(program)FundersAccountability—directfrom JISC/Academy toHEFCE/DIUS so theyknow where the moneywent (assume they'll dothis by aggregation)Structured in RSS feedie UKOER tagHost platform must allow tag to be addedand included in RSS feedAccountability—indirect.The funders might wantusers to be aware of their role in the release of thisresource.Human readable? Acknowledgementwith link to info about programme?End UsersMight be a factor inresource selection (e.g. if they know UKOER funded good stuff)Contributing partner To manage their stuff (maybe by aggregation)Encoded, in RSS feed and/or in host’scontent management metadata.A tag for each contributor would help. page 3 of 8
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...