From OntologPSMW

Jump to: navigation, search
[ ]


Ontolog Wiki and File Management Procedures     (1)

Ontolog sessions require managing not only the session page on the wiki but also related files (such as slide decks for speakers) as well as the metadata annotations for the wiki and files. This page describes the procedures and conventions for file name and metadata managment. All the procedures aand conventions on this page were developed by PeterYim. Sessions also require processing the chat room conversations and the audio recording (if the session was recorded). The procedures for processing these have been well documented at Ontology Summit 2014 Process. See also the excellent slide presentation by Peter Yim and Christine Kapp.     (1A)

Session Workspace     (1B)

The workspace consists of the following:     (1B1)

  1. The wiki page     (1B2)
  2. A directory and subdirectory on the webdav server     (1B3)
  3. A chat-room label     (1B4)

Submission of Slides     (1C)

A slide deck must be in pdf format. Additional files may be submitted in other formats, such as ppt, pptx or odp.     (1C2)
  • Conversion from the other formats can be done by the production crew, but can be problematic.     (1C3)
Slide numbers    (1C4)
The slides should be numbered consecutively starting with the first slide.     (1C5)
Metadata    (1C6)
Populate the metadata using the file or document properties.     (1C7)
Speaker Advice    (1C9)
A quick reference for your speakers is to insist that they read through the page at: ... especially the section labeled 'For the SPEAKERS'     (1C10)

Peer Review     (1D)

  1. As slides are received, they are uploaded to the wip subdirectory.     (1D1)
  2. The slides are then peer reviewed.     (1D2)

Slide Deck Processing     (1E)

  1. Rename the filenames to conform to the naming convention, if necessary.     (1E1)
  2. Remove the version designation.     (1E2)
  3. Fill in missing metadata, and modify metadata to be consistent for all presentations in one session and in a series.     (1E3)
  4. Add slide numbers, if necessary.     (1E4)
  5. Convert to pdf format, if necessary.     (1E5)
  6. Copy to the main directory from the wip directory.     (1E6)
  7. Add a link to the session page     (1E7)
  8. Notify the session chair(s) and all speakers so they can do a final review.     (1E8)
  9. The notification also acts as a final reminder.     (1E9)

Conventions     (2)

Metadata for Slides     (2A)

Filename     (2A1)
The name of the file should use this convention: {description}--{author}_{date}{version}.{extension}     (2A2)
  • The description is generally the title of the slide deck. Separate words with hyphens, and separate multiple lines in the title with underscores.     (2A3)
  • The author is written in CamelCase without any hyphens or underscores. Multiple authors are separated by hyphens.     (2A4)
  • The date is written in the format YYYYMMDD.     (2A5)
  • The version is for the wip versions, not for the final version. The versions are "a", "b", etc.     (2A6)
  • For example, Ontolog-Going-Forward_Background-n-Vision--KenBaclawski_20140626a.pdf     (2A7)
Same as in the slide deck.     (2A9)
  • For example, Background and Vision - Thu 2014.06.26     (2A10)
  • Don't include author(s) as they are specified in another metadata property.     (2A11)
Use the format {role}: {name}, {name} ... (where the role is optional)     (2A13)
{session title}: {description} - {date}     (2A16)
  • For example, ONTOLOG Going Forward: new ONTOLOG Board of Trustees meets the community - Thu 2014.06.26     (2A17)
The URL for the read-only location of the file.     (2A19)
These are specific to the presentation.     (2A22)

Metadata for the Audio Recording     (2B)

This is for the Audacity metadata.     (2B1)

Artist Name    (2B2)
{name} ({role}), {name}, ...     (2B3)
Track Title    (2B5)
{session title}: {description}     (2B6)
Album Title    (2B7)
{session title}: {description} - {date}     (2B8)
  • Keep the same across all artifacts - slides, audio recording, etc.     (2B9)
  • For a series, keep pattern across the other sessions.     (2B10)
Track Number    (2B11)
{number}     (2B12)
The year of the session.     (2B16)
The proper format for a copyright is {copyright symbol} {year} {company} All Rights Reserved. {link to detailed license}     (2B20)

Metadata for the Audio Recording Archive     (2C)

This is for the post-processed mp3 format.     (2C1)

ID3v2 Tags     (2C2)

Disc# 2014     (2C2B)

Title: ONTOLOG Going Forward: new ONTOLOG Board of Trustees meets the community     (2C2C)

Artist / Album Artist / Orig. Artist ONTOLOG Going Forward: new ONTOLOG Board of Trustees meets the community     (2C2D)

Album ONTOLOG Going Forward: new ONTOLOG Board of Trustees meets the community - Thu 2014.06.26     (2C2E)

Year 2014     (2C2F)

Genre Speech     (2C2G)

Comment (cc) 2014 Ontolog, ONTOLOG Board of Trustees, some rigths reserved; ref.     (2C2H)

Composer: Ontolog Board of Trustees, Leo Obrst, Amanda Vizedom <--[BoT, organizers and co-chairs]     (2C2I)

Publisher: Ontolog, Ontolog Board of Trustees, Ken Baclawski, Christi Kapp, Amanda Vizedom, Leo Obrst <--[list production crew]     (2C2J)

Copyright (cc) 2014 Ontolog, ONTOLOG Board of Trustees, some rigths reserved     (2C2K)

Encoded Christi Kapp (include affiliation, if this is a donation by that organization)     (2C2M)

BPM __ <--[leave blank]     (2C2N)

Track Gain __ <--[leave blank]     (2C2O)

Album Gain __ <--[leave blank]     (2C2P)

ID3v1 Tags     (2C3)

Title ONTOLOG BoT debut - 2014.06.26     (2C3B)

Artist ONTOLOG Trustees, participants     (2C3C)

Album ONTOLOG Going Forward     (2C3D)

Year 2014     (2C3E)

Genre Speech     (2C3F)

Comment (cc) 2014 ONTOLOG BoT     (2C3G)

Forum Posts (Email)     (2D)

  • To�� get proper purple numbering in the message archives, use "plain text" and leave a blank line between paragraphs.     (2D1)

New Member Procedures    (3)

  • Subscribe the new member to the [ontolog-forum] list     (3A)
  • subscribe the new member to the [ontolog-invitation] list     (3B)
  • look the new member up on the web and initialize a namesake wiki page for them     (3C)
  • include this on the namesake page for details about how to create a login and edit the wiki.     (3D)
  • write the new member a welcome message     (3E)
  • in that message, prompt the new member to complete and return the member online profile/survey form too [1]     (3F)

Board of Trustees Meeting Procedures    (4)

Duties of Chair    (4A)

  • If the next meeting date for the BoT is not yet established, then after checking with the conference bridge steward (currently MichaelGruninger), determine potential dates for the next meeting. You can confirm (via email) with BoT members that they have no constraints, and then keep or modify the date of the next BoT meeting, as necessary.     (4A1)
  • Add the meeting to the Ontolog Forum Google Calendar if it is not already present.     (4A2)
  • Notify (via email) BoT members of the date of the next BoT meeting.     (4A3)
  • Notify (via email) the designated Scribe for the next BoT meeting. Let that person know they will thereby be the Chair for the subsequent BoT meeting. We typically follow the order for designated next Chair and Scribe by the order of the BoT members at, which is ordered alphabetically by first name (or forename) of the BoT member. If the next Scribe cannot assume that role (due to schedule conflict, etc.,) then select the next person in order and request they become the Scribe and thereby the subsequent Chair. If the next person, in turn, cannot become the Scribe, then because we have no established procedure, request (via email) guidance from the other BoT members. In general, if a particular BoT member who is designated to be a Scribe (and then, subsequent Chair) cannot fulfill that duty, then that person becomes the primary candidate for the subsequent Scribe role (and following that, the subsequent Chair). Chairs should always confirm with the designated Scribe that that person can fulfill the Scribe (and subsequent Chair) role.     (4A4)
  • Create new wiki session page for upcoming BoT meeting, using form of By simply typing in a non-existent page such as, a page with that name will be created.     (4A5)
  • Create the requisite desired structure of the session page by copying the structure of an old session page (after logging into the wiki for that page and selecting Edit). Then login to the new page, select Edit, and paste that structure into the edit form. Modify that structure as you see fit. Also update it with new information, confirming that you have no undesired old information and have only desired links.     (4A6)
  • To establish the chat session of the next BoT meeting, designate the chat page to be in this format: You do not have to initialize such a page. By simply designating it and using it, you create that chat page.     (4A7)
  • Update BoT home page ( with a link to the new BoT session page you just created. Place it under "Key Dates to Note". After the BoT session has taken place, notify Scribe to move it to the "What's New" section.     (4A8)
  • Update the Ontolog Forum Google Calendar entry for the event with the link to the session page.     (4A9)
  • Notify (via email) the BoT members of the existence of the new session page, invite them to add to the emerging Agenda.     (4A10)
  • Update the new session page's Agenda as necessary, prior to the next session.     (4A11)
  • Confirm (via email) that some BoT member can capture the audio archive of the coming session (for now, Ken Baclawski is handling the recording, if he is attending). If that person is not known, query (via email) the BoT members about who can do this.     (4A12)
  • Confirm (via email) with other BoT members if you need other services and who can provide such.     (4A13)
  • Prior to the actual BoT session, confirm that you know the adminstrator/host code for the bridge telecon phone call, since as Chair, only you can permit the bridge telecon to take place. If you do not know this code, request it (via email) of the BoT members. Only BoT members should know this number, so please do not promulgate more widely.     (4A14)
  • Notify (via email) BoT members 1-2 weeks in advance about the next BoT meeting. Provide a draft agenda. Remind them to add agenda items they want to discuss; and add themselves to the list of expected attendees, or notify you (and then you add them). Remind them to offer regrets if they cannot attend, and then you add their names to the Regrets.     (4A15)
  • Remind BoT members again 1 (or 2) day(s) prior to the next BoT meeting about that meeting.     (4A16)
  • immediately after the session is adjourned, from the soaphub chatroom "Actions" window, do the following:     (4A17)
    • execute "Get the list of attendees" (by clicking on said link)     (4A17A)
    • mailing a copy of the chat-transcript to the [ontolog-trustee] mailing list (by entering "ontolog-trustee[at]" to the "Mail transcript" field and then invoke "send")     (4A17B)
    • copy and paste the content of the chat window (i.e. the chat-transcript) and save it locally, for your use in preparing the minutes     (4A17C)
  • within a day or two after the session:     (4A18)
    • make sure the audio recording has been posted     (4A18A)
    • update the session page with the proceedings of the session     (4A18B)
    • update the session page with the "decisions/resolutions" and "action items" from the session     (4A18C)
    • when done, make a post to the [ontolog-trustee] mailing list to notify fellow trustees that the proceedings have been captured, remind them of the action items, and instigate other necessary follow-ups.     (4A18D)

Duties of the BoT Meeting Scribe    (4B)

Recording Sessions     (5)