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-2009 Because Phil said "It would be useful first to define what information about a resource you 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 through Google or otherwise, etc. etc. Format: includes free text for humans to read (which is incidentally what Google works from) and encoded text for machine operations (e.g. XML, RSS, HTML metatags, microformats, metadata embedded in other formats or held in the database of 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 point to an actual instantiation that is at least planned, if not under development or implemented.

This work is licensed under a Creative Commons Attribution 2.5 License.

Metadata requirements for EngSC OER project

Phil Barker & Lisa J Rogers Heriot-Watt University

Characteristic For Whom Title End User

Why? Aid resource discovery and selection

Format Human readable. In resource, as title page and as running header; or on resource display page. Formatted as heading / title or running header.

Notes Needs to convey maximum information in minimum space, e.g. subject + level formula of "Perl for beginners" Host platforms must allow title to be specified on upload and handle display on resource page and metadata in feeds. Do any host systems extract embedded metadata other than Flickr from images?

In structured markup <title>, <h1>, suitable word style / format. May be worth adding to EXIF metadata of images. Contributor Easy reference, to allow rapid identification and location of known resource. If search is via Google then format as above. If search is via API then must be in host's content management metadata. RSS/ATOM item-level title <item><title> Human readable. In resource as Should be short and key-word intensive; abstract, or on resource display page. including content subject and level.

Proj Mngr Aggregators Description End User Display of available resources Search & Selection

page 2 of 8

Metadata requirements for EngSC OER project

Phil Barker & Lisa J Rogers Heriot-Watt University In structured markup <meta description = ""> if that can be done automatically.

Aggregators Provenance (program) Funders

Display to users Accountability—direct from JISC/Academy to HEFCE/DIUS so they know where the money went (assume they'll do this by aggregation)

In RSS/ATOM item-level description <item><description> Structured in RSS feed

Host platforms must allow description to be specified on upload and handle display on resource page and metadata in feeds. ie UKOER tag Host platform must allow tag to be added and included in RSS feed

Accountability—indirect. Human readable? Acknowledgement The funders might want with link to info about programme? users to be aware of their role in the release of this resource. End Users Might be a factor in resource selection (e.g. if they know UKOER funded good stuff) To manage their stuff (maybe by aggregation) Encoded, in RSS feed and/or in host’s A tag for each contributor would help. content management metadata.

Contributing partner

page 3 of 8

Metadata requirements for EngSC OER project Provenance (source institution) For attribution.

Phil Barker & Lisa J Rogers Heriot-Watt University In text, with author information (top/front of document?) and with © info (end/back of document), or on resource display page. Encoded, in RSS feed with © and licence info. Would be best if host system knew who contributor was and had their profile, i.e. Flickr photostream or YouTube channel for each contributor. Many (most? all?) hosts use this info for attribution and © ownership info.

Proj Manager

To monitor the partners' contributions (by aggregation) May want stuff from specific HEI

Encoded, in RSS feed and/or in host's content management metadata. As searchable text, or As an association between resource and information about institution

End User

Provenance (source course) Provenance (project)

End User

May be interested in In text in resource description known course; also useful for selection as indicator Link to course web page of subject and level. Accountability—direct from us to them so we can tell them what we've done with their money (assume we'll do this by aggregation) Structured in RSS feed or API ie EngSCOER tag and logo Host platform must allow tag to be added and included in RSS feed Desirable for host platform to allow some form of pooling for resources from several contributors.

Funders

page 4 of 8

Metadata requirements for EngSC OER project

Phil Barker & Lisa J Rogers Heriot-Watt University

Accountability—indirect. Human readable? Acknowledgement We might want users to with link to info about project.? be aware of our role in the release of this resource. End Users Might be a factor in resource selection (e.g. if they know EngSCOER delivered good stuff) To manage their stuff (maybe by aggregation) For attribution. Encoded, in RSS feed and/or in host's Difficult to think how host platforms content management metadata. i.e. might manage this and institutional <dc:creator> provenance in a way that will be encoded in feeds. – separate account for each author and pool by institution may be In text, on title page (top/front of problematic in terms of number of document?) and with © info authors. (end/back of document), or on resource display page. Encoded, in RSS feed with © and licence info. so that it is passed on to aggregators. . i.e. <dc:creator> End User Selection or search is author is known to user Selection—is it current In Resource, Front page

Provenance (author)

Contributor

Creation / revision Date

End User

In text, on title page (top/front of document?), and/or on resource display page Encoded at item level in RSS feeds.

Beware of hosts using upload date as default.

Aggregator

Selection—is it current

page 5 of 8

Metadata requirements for EngSC OER project Contributor Version Control (dunno, problematic) accountability? See what’s recently been added Selection Know rights restrictions Selection Protect Rights Automatically generated In RSS Feed Automatically generated <dc:format>?

Phil Barker & Lisa J Rogers Heriot-Watt University

Date of Upload

Proj manager? End User/ Aggregator

Format Licence

End User End User Contributor

In text and with © info (end/back of document), or on resource display page. Encoded, in RSS feed so that it is passed on to aggregators

cc-by See http://wiki.creativecommons.org/RSS_1.0 for guidance on embedding CC Licences in RSS 1.0 feeds. Host must handle these as tags.

Subject Keywords

End User

Discovery and selection

Keywords in abstract / description Encoded, in RSS feed so that it is passed on to aggregators.<dc:subject>?

Duration

End User

Discovery and selection: is resource

In description, automatically generated (e.g. by YouTube) or implicit (e.g. for image) Encoded, in RSS feed so that it is passed on to aggregators

Third Party Rights

End User

Know rights restrictions

How does host platform manage/acknowledge these rights.

page 6 of 8

Metadata requirements for EngSC OER project Third Party Contributor Attribution Correctly Attributed 3rd Parties

Phil Barker & Lisa J Rogers Heriot-Watt University In text and with © info (end/back of document), or on resource display page. Encoded, in RSS feed so that it is passed on to aggregators

How can this be used? Source URL

End User End User

Understand how resource Could form part of the description was intended to be used within text/abstract or on resource description page. May wish to link to Link in Resource or on resource original resource rather description page. than a copy elsewhere or to check for a newer version. May be curious as to origin of the resource. They may wish not to incur data charges for downloading large files (i.e. if they were using mobile broadband) Usually automatically generated by system, may appear as text next to download button

File Size

End User

Language

End User

Selection, to know if they Can usually select language within can understand the web 2.0 service. Can sometimes be resource automatically generated. Easy reference, to cite the The URI of the resource and is resource or for attribution automatically generated by the system. Should be a persistent link.

Identifier

End User

page 7 of 8

Metadata requirements for EngSC OER project

Phil Barker & Lisa J Rogers Heriot-Watt University

page 8 of 8

Sign up to vote on this title
UsefulNot useful