[University home]

Time-based Media Application Profile

Project Outputs

From Tbmap




This page is used to outline material and approaches associated with the project during its progress, and on completion of the project to provide access to the deliverables in their final, as well as their working, form.

Community Acceptance Plan

  • Requirements Gathering
    • Desk work review of known existing practice, profiles and specific orientations for TBM within HE.
    • A cross-section of known experts from different TBM-based professional fields will be identified and invited to discuss current and future examples of use and requirements from their fields
    • A core set of cases and examples will be prepared to check compatibility with testing against a proposed model and developing a Functional Requirement Specification.
    • Discussion and input will be sought from working and feedback groups.
    • Material and approaches to building the profile will be revised based on input received.
  • Working/Feedback Group
    • Representatives should come from repository and repository support-oriented groups as well as TBM professionals from HE and associated industries.
  • Meetings
    • Documents
    • Particpants
  • Wider Activities

Introduction to the Consultation Materials

Stages of development prior to producing a TBM Application Profile include:

  • scoping Functional Requirements,
  • defining the role of the Application Profile,
  • producing a Functional Requirement set to underpin development of a Search & Discover TBM Application Profile,
  • generating a model

The consultation documents provided here have been designed to open the work at various stages to discussion around the questions, assumptions & concerns (qac) that arise during the project activity and to try to seek consensus, recommendations and/or agreement around the direction the project is taking. The material presented has been loosely grouped into discussion areas for convenience, and each includes at least a general information document and a supplementary document with a brief introduction to the section and a list of initial qac's arising.

It is recognised that a profile cannot be all things to all people, so a pragmatic first cut with potential for extension, fit for post-production search & discovery purposes, and that is compatible as far as possible with prior TBM-related work, is sought.

Most of the materials referred to in the documents are indicated from Reference Sources.

Access to Consultation Materials and Discussion Spaces

Determining Functional Requirements

Application Model


Application Profile

Example Description Sets

Summary & Additional Documents

Scoping Material: Definition Phase

  • TBMAP Definition Phase Final Report [pdf][doc]
    • Information Summary 1: Executive Overview of TBMAP Work [doc]
    • Information Summary 2: TBM Source Material
      • Item 2a: Examples and References for TBM Use in HE [doc][working]
      • Item 2b: Other Archives and Collections [doc] [working]
    • Information Summary 3: Application Profile Building Reference Sources [doc][working]
    • Information Summary 4: Functional Requirement & Use Case Related Material
      • Item 4a: Functional Requirements & Use Cases [doc][working]
      • Item 4b: Functional Requirements Summary [doc][[html]
Prototype Development Material: Build Phase
  • TBMAP Build Phase Final Report [pdf][doc]
    • Information Summary 7: Application Model Related Material
      • Item 7a: Application Model Overview [html]
      • Item 7b: Application Model Examples [html]
    • Information Summary 8: Build Related Material
      • Item 8a: Description Set Profile & Usage Guidelines [html]
      • Item 8b: TBM Terms Vocabulary [html]
      • Item 8c: Encoding Guidelines [html]
      • Item 8d: TBM DCAP, OAI-PMH and Simple DC [html]
      • Item 8e: Example Description Sets [html][working]
  • [working] refers to draft material that is already represented elsewhere on this wiki. If there is a collated version in another format, then that supercedes the working material, and should be treated as definitive.
  • [html] refers to final versions represented elsewhere on this wiki. In this case, the wiki and any collated versions are treated as equivalent and the wiki version should be treated as definitive.
  • [other format] indicates the version in an alternative format (e.g. *.pdf, *.doc) that has been made available as the final project document, based on a working draft held elsewhere on this wiki.

|  This page was last modified 14:03, 1 October 2009. | This page has been accessed 42,335 times. |