KIM-DINI-Technology-Watch-Report/Editorial-Board-Meeting-2008-04-08

TWR

Time and Venue Tuesday, April 8 2008 13h00 to 17h00 MPDL Berlin

Participants

Tom Baker (SUB)

Stefan Farrenkopf (SUB)

Tanja Friedrich (MPDL)

Andreas Gros (MPDL)

Justine Haeberli (SUB)

Traugott Koch (MPDL)

Laurent Romary (MPDL) - via VC

Apologies for absence were received from

Reinhard Altenhöner (DNB)

General

 * DINI Beirat response to the KIM suggestions (Chair take-over)
 * AI: Laurent asks R. Altenhöner about the Chair issue


 * Progress on the KIM-DINI-Event at the DINI Conference
 * AI: Laurent and R. Altenhöner try to reserve a slot for the DINI conference in October


 * Status on further Editorial Board Members, e.g. Tobias Steinke, Markus Enders
 * Stefan talked to Markus Enders: He's currently working for the British Library. He is interested to work on the editorial board, but has to talk to his employers, and will report back to us. He worked for the Digitization Center in Göttingen and has a lot of expertise on Metadatadescriptions of complex objects (by means of METS, etc.).
 * Stefan Strathmann is also interested and can contribute to the editorial board by providing a broad overview of the field of long-term archiving and can identify new topics and people to write on them.
 * AI: Justine asks Christine Frodl to suggest a "standards-person" from the DNB who could participate in the editorial board.

Work plan 2008
Previous work plan for 2008
 * The plan was to have the second edition in April, and have the third edition in October.
 * The established workflow was 2 months time for the authors to submit their contributions + 1 month of finalizing

Todo list for Editors
 * work on topic spectrum for deep articles
 * initiate topic lines (e.g. special issues on specific topics with invited contributions)
 * initiate news spectrum
 * generate an overview on standard activities without digging too deep
 * AI: The editors establish a page with guidelines for authors

General todo list:
 * define quality criteria for contributions
 * establish a basic typology for contributions, to be able to describe an ideal article to authors with a focus on interoperability.
 * define a rough target number of articles for each topic.
 * define a loose schedule for issues (e.g. for special topics, topic lines, etc.)
 * establish a feedback possibility for readers to suggest new topics, and thematic lines
 * get a test implementation for all parts (wiki + blog),
 * consider archiving options
 * anti-spamming
 * structuring

Wish list for blog features:
 * Local installation
 * Individual stories and printing
 * Permalinks
 * URIs for each stories
 * Spam prevention (Captchas)
 * Access to comments only over a link to not have to print them while printing the article
 * Editing of comments
 * Cleartext export of articles (transform links to URL in footnotes)
 * PDF export
 * Mediawiki compatible (because of editing, exporting)
 * blog.mediawiki.de works with wordpress
 * Costs


 * AI: Andreas and Tanja create a decision matrix for the blog software
 * AI: Andreas creates a KIM TWR EB page
 * AI: Andreas creates a mailing list for the EB + citeable archive + fulltext search


 * Future meetings: standard: Telcon+IRC oder VC; Face2Face meeting 1 or 2 times per year.
 * AI: Andreas: check back-end for IRC or other chat software that permits group chatting

URL for TWR:
 * Service should hosted at MPDL, because the technical work is done there
 * If MPDL ceases to exist, actions for further maintenance/service have to be taken. Therefore, we have to talk to DNB or SUB for this emergency case.


 * AI: Andreas polls on the URL issues (independent domain, KIM domain, or DNB/SUB domain)
 * AI: Tanja and Andreas write a note for the KIM website; for authors: ... in case of interest for contributing please contact the Editorial Board, don't send articles.

Workflow for contributions

 * communication between EB and authors per E-Mail
 * writing of contributions by authors directly in the wiki (invited contributions)
 * or sending contributions to technical editors per E-Mail
 * technical editors transform such contributions into wiki pages and
 * assign topic editors to the contributions
 * topic editors are responsible for review and content supervision
 * technical editors support structural/technical editing by authors in the wiki
 * composition and publication of special/thematic issues are discussed by the editorial board
 * corresponding topic editors have to approve contributions to such issues
 * articles receive their current status from a fixed list of statuses
 * all editors read the contributions (at least in the beginning, to develop a detailed profile)
 * all editors comment on the contributions

TWR topic suggestions

 * Invitations of contributions should emphasize a focus on interoperability
 * A definition of what KIM's understanding of interoperability is should be obvious to the reader/author
 * In each article readers should get a concise answer to an interesting question
 * Editors pose the questions so that the TWR can establish its own character
 * Articles will be split in two facettes: "topic" and "level of detail" (two such levels will most likely be enough)
 * AI: During DC-2008 a wider range of possible authors will be approached by the editors. Therefore, some articles should already be online. Workshop organizers could write something about their workshops.

-- Andreas Gros 11:56, 14 April 2008 (CEST)