DELOS:Schema description of events

From Wiki

Contents 1 Preliminary Schema descriptions of Digital Library Events 1.1 Schema for sessions 1.2 Schema for events 1.2.1 Further definitions/assumptions 1.3 Schema for content 1.4 Critics

Preliminary Schema descriptions of Digital Library Events

Schema for sessions

A session is the surrounding object for all events that happen within a digital library, either initiated by a user or usergroup, but also by the system. We should try to gather and store the current context through several attributes:

• General session attributes
  • SessionID - a unique sessionID
  • Start timestamp - timestamp in millisec to identify the begin of a session
  • End timestamp - timestamp in millisec to identify the end of application

• Session - A session has always the following attributes:
  • Initiator: Inititor of application (system/user), Using Daffodil usually an user initiated the application
  • System: Identifies the evaluated system (e.g. "daffodil")
  • Context: Contains the intention and involved events

• context - A context has always the following attributes:
  • Current worktask
  • Current searchtask
  • User: User data like age, working place, gender etc.
  • event: A set of involved events

Sessions XSD file

Schema for events

• General event attributes
  • EventID - unique event ID
  • Start timestamp - timestamp in millisec to identify the beginning of an event
  • End timestamp - timestamp in millisec to identify a return
  • Service - used service logged in DB

Currently we only describe events as system events. We identified the following event types:

• Search-Event
  • A search event has always the following attributes:
    • Input: A query, given in any form
    • Output: One or a set of a digital library object(s)
    • Collection: This is the collection the query is run against

• Navigate-Event
  • A navigate event has always the following attributes:
    • Input: A single digital library object
    • Output: A set of digital library objects, or a summary of digital library objects
    • Collection: The used collection

• Browse-Event
  • A browse event has always the following attributes:
    • Input: A possible empty set of digital library objects
    • Output: A set of digital library objects, or a summary of digital library objects
    • Collection: The collection that is browsed
    • Method: Definition of browsingmethod (e.g. slide)

• Inspect-Event
  • An inspect event has always the following attribute:
    • Input: A single digital library object

• Display-Event
  • A display event has always the following attributes:
    • Input: A possible empty set of digital library objects
    • Sort: The used attributes and predicates
    • Visual: Description of attributes of Shniderman (1D,2D,3D,time,multi-dimension,tree,network), how the data is presented.

• Store-Event
  • A store event has always the following attributes:
    • Input: A set of digital library objects
    • Target: Place where the object is stored. The object can be stored
      • externaly: as a file on a harddisk
      • printed: via a printer
      • internal: e.g. within the personal library of Daffodil.

• Annotate-Event
  • A annotate event is used to annotate a digital library object. This includes textual annotations, like comments, reviews or summaries, but also ratings. The following attributes are included:
    • Input: A set of digital library objects
    • Content: The actual annotation
    • AnnotationType:
      • comment
      • summary
      • review
      • rating

• Authoring-Event
  • A authoring event has always the following attributes:
    • Input: A single digital library object
    • Target: The storing destination after creating an object

• Communicate-Event
  • A communicate event has always the following attributes:
    • Content: content of communication (e.g. chatlog)
    • Media: used mediatype (e.g. chat, whiteboard)
    • Type: synchron/asynchron and local/network

• Help-Event
  • A help event has always the following attributes:
    • Input: The actual context, service or graphical tool
    • Inhalt: The content of help or reference
    • Type: A help event can be of type suggestion, userInteraction or systemDialog.

Further definitions/assumptions

• events include events on the GUI level (which have a source, or trigger, might incorporate direct user input, drag-and-drop action, menu or button selections, right-click actions, etc.), events on the semantic level (search for papers by a specific author, browsing down one level with the conference browser, looking up a definition of a term, etc.), and maybe events on the user level
• events can be triggered by the system or a specific user (the user has to identified for collaborative sessions)

Events XSD file

Schema for content

Content XSD File

Critics