1 / 6

IMS CHARTER FOR RESOURCE LIS INTEROPERABILITY

IMS CHARTER FOR RESOURCE LIS INTEROPERABILITY. Nicole Harris, Project Officer London School of Economics. Premise. Arose from queries from 07/02 projects on metadata mailing lists, and from discussion at last programme meeting.

khan
Download Presentation

IMS CHARTER FOR RESOURCE LIS INTEROPERABILITY

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IMS CHARTER FOR RESOURCE LIS INTEROPERABILITY Nicole Harris, Project OfficerLondon School of Economics

  2. Premise • Arose from queries from 07/02 projects on metadata mailing lists, and from discussion at last programme meeting. • “No metadata standard for the description of resources associated with courses or sites instantiated within virtual learning environments or course management tools.”

  3. Rationale • Enable the creation of tools for the generation and exchange of resource lists according to a standard format; allows for the incorporation of resource list data into other e-learning tools. • Future efforts to integrate enterprise learning and library course reserves system will not need to rely on proprietary systems. • Leverages federated searching tools to capture records for resource lists. • Establishes the potential for a unified resource list creation workflow.

  4. Functional Requirements ------------------------------------------------------------- RESOURCE SOURCE IDENTIFIER: = The Source of a resource, e.g. catalogue or index. RESOURCE IDENTIFIER: = A unique identifier for the resource. RESOURCE TYPE: = book article etc. SOURCE: = Data required to cite the resource. ANNOTATION: = Information added by list owner. TIME REQUIRED: = Date range resource is relevant to a course. REQUIRED / OPTIONAL: = Recommendation from list owner for application. LOCATOR: = Locators associated with a resource. EXTENSIONS: = vendor extensions to the specification. --------------------------------------------------------- LIST RESOURCE LIST IDENTIFIER: = A unique identifier for the list. RESOURCE LIST CREATOR: = Creator of list. RESOURCE LIST OWNER: = Owner of list. RESOURCE CATEGORIES: = Definable categories for list. NESTED RESOURCE LIST: = May subsume additional resource lists. EXTENSIONS: = vendor extensions.

  5. Out of Scope • Persistent Locators. • Access Management. • Association of Course Identifiers. • Item-specific association of resources within LMS to resource lists. • Update transactions. • Definition of transport protocols. • Annotations as separate objects.

  6. Where Next • Howard Noble and Lorna Campbell to attend IMS conference 7 -11 July in Boston. • Project Kick-off to organise who does what. • Good to have schemas and processes from projects currently using / implementing resource lists. • See: Cetis / JISC listservs for more formal request for information. • Project team keen to work with JISC.

More Related