JATS-Con Logo

JATS-Con 2018 Schedule with Abstracts

April 17, 2018

8:00-9:00

Registration

9:00-9:15

Welcome and Introductions

9:15-9:45

Fighting the "Inevitable" Expansion of the JATS Tag Sets

B. Tommie Usdin, Mulberry Technologies, Inc.

9:45-10:30

Listen up! Is it time for systems to pay attention to attributes?

Mary Seligy, Canadian Science Publishing

Virtually none of us produces attribute-free content, and all of us rely on at least a few attributes for internal processing and publishing to our own websites. Outside of our own publishing systems, sensitivity to attributes and their values is patchy. But this is at odds with a world in which content exchange and reuse are more important than ever in the shared scholarly publishing infrastructure, much of which is supported or could be supported by attributes. In this presentation, we'll look at the current state of attribute insensitivity among systems and the changing role of attributes in scholarly publishing, with the aim of starting a conversation about why and how we need to address the challenges around attribute insensitivity in systems.

10:30-11:00

Coffee Break

11:00-12:30

Best Practices Panel

11:00-11:20

Introduction

Jeffrey Beck, NCBI/NLM/NIH

11:20-11:40

JATS4R Overview

Melissa Harrison, eLife

JATS4R (JATS for Reuse) is a working group devoted to optimising the reusability of scholarly content by developing best-practice recommendations for tagging content in JATS XML.

11:40-12:00

STS4I Overview

Gerrit Imsieke, le-tex publishing services

STS4I (Standards Tag Suite XML for Interoperability) is a community-driven effort to provide tools and document best practices for creating and processing STS XML documents.

12:00-12:30

Discussion

12:30-1:30

Lunch

1:30-3:00

JATS Vendor Showcase

1:30-1:50

Data Conversion Laboratory Inc.

Mark Gross, Data Conversion Laboratory, Inc.

1:50-2:10

Ictect, Inc.

Pradeep Jain, Ictect Inc.
Lisa Rupe, Ictect Inc.

2:10-2:30

Typefi Systems, Inc.

Chandi Perera, Typefi, Inc.

2:30-2:50

Inera, Inc.

Bruce Rosenblum, Inera, Inc.

3:00-3:30

Coffee Break

3:30-4:15

MECA―Manuscript Exchange Common Approach

Caroline Webber, Aries Systems Corporation
Sally Ubnoske, Aries Systems Corporation
Joel Plotkin, eJournalPress

Authors are irritated at time, effort, delays when re-submitting articles. Reviewers' time is wasted when reviews are re-done or replicated. New publication flows demand transfers to/from preprint servers. Each workflow system has to implement separate transfers to each other system―these "pairwise" transfers, all using different XML and transfer "packages"― are inefficient. A common approach to moving manuscripts solves these use cases and can also solve some additional workflow problems. All we need is for a group of competitors to collaborate!

4:15-5:00

Using JATS to Harmonize JSTOR's Journal Metadata Capture

Jonathan Ponder, ITHAKA (JSTOR)

JSTOR is in the process of implementing a new XML metadata specification for journals based on the Journal Archiving and Interchange tag set. This new JSTOR journal metadata specification is a key part of a larger effort to unify JSTOR's metadata capture, production, and ingest across journal content, regardless of source input or business product. Up to now, JSTOR journals have used a combination of an in-house XML DTD and various versions of the NLM XML DTDs, depending on source input and business product, but now we are updating the metadata specifications we use to cover all journals in a single specification that complies with the latest JATS version. In this presentation, I will briefly describe JSTOR's production context, which involves processing current to very old journal issues from a wide range of disciplines including the humanities, social sciences, STEM, law, economics, and business. Next, I will discuss our move to a JATS-based specification and, in particular, the new specification document itself, which does the following: 1) defines a subset of JATS tags to use for JSTOR journals, 2) outlines the XML model and other technical requirements according to JATS rules, 3) outlines additional JSTOR editorial and business rules, which comply with JATS, 4) covers the processing of print source, PDF source, and full-text XML source, and 5) defines an Issue XML file model and a Pages XML file model to be used for scanned print source material. Finally, I will discuss some specific examples of changes and additions to our metadata specification in this update to the JATS standard and some of the benefits and challenges of making this change to JATS.

April 18, 2018

9:00-9:45

What it takes to get into the NCBI Bookshelf

Martin Latterner, NCBI/NLM/NIH
Stacy Lathrop, NCBI/NLM/NIH

The NCBI Bookshelf is an online archive of over 6000 books and documents in life science and healthcare. Full-text content is submitted in XML by participating authors, editors, funders, sponsors, and publishers. This paper describes the requirements for participation: What is the scope of the collection, what types of content are eligible, and what are the scientific and editorial quality standards? Special emphasis is placed on the technical evaluation process: How do participants submit XML and what are the minimum requirements? We will talk about details of the XML submission process, about the challenges and obstacles participants may encounter, and about what NCBI is doing to help during the process.

9:45-10:30

Driving RDF graph creation through novel JATS markup utilizing multiple compound keyword groups

Jack Bruce, Access Innovations, Inc.
Win Hansen, Access Innovations, Inc.

During 2017, Access Innovations began designing and implementing a novel approach to keyword groups applied to scholarly published journal content including research articles, conference proceedings, standards, and periodicals. Additions of compound keyword groups and named-content markup within the full-text enabled robust RDF triplestore creation for use in front-end search applications.

10:30-11:00

Coffee Break

11:00-12:30

JATS Mini Tagging Tutorials

Jeffrey Beck, NCBI/NLM/NIH
Gerrit Imsieke, le-tex publishing services
Deborah A. Lapeyre, Mulberry Technologies, Inc.
Evan Owens, Cenveo Publisher Services
Laura Randall, NCBI/NLM/NIH
Bruce Rosenblum, Inera, Inc.
B. Tommie Usdin, Mulberry Technologies, Inc.

12:30-1:30

Lunch

1:30-3:00

JATS Open Session

3:00-3:30

Coffee Break

3:30-4:15

Adaptation of JATS XML for Japanese humanities papers

Hidehiko Nakanishi, Nakanishi Printing Co. Ltd.
Tsuyoshi Yamamoto, Nakanishi Printing Co. Ltd.
Nao Hattori, Nakanishi Printing Co. Ltd.

In response to JATS becoming Multilingual compliant, J-STAGE, a Japanese e-journal platform, adopted JATS as a schema in May 2012. Since then, Japanese articles written in JATS have been published in J-STAGE. Attempts to create online journals in their national languages are also progressing in Korea and China.

Among these East Asian languages which do not use the Latin alphabet, Japanese is a very complicated writing system thhat uses "kanji", which are ideograms, and "kana", which are phonetic characters. As I reported in JATS-CON 2015, although there were difficulties, it was indeed possible to express these characters via JATS. However, most of the Japanese papers published so far using JATS are STM adapting horizontal writing systems, which are structurally consistent with English papers. Most of them only replace Latin letters with Japanese characters. In this presentation, we report on the history of creating vertically oriented Japanese humanities articles in JATS XML. Although this process cannot yet provide an environment of the full text, I will consider issues in the multilingual environment, including Japanese, through this experience.

4:15-5:00

The False Security of Closed XML Systems

Jeffrey Beck, NCBI/NLM/NIH

Creating and using XML documents in a closed system gives a false sense of "All's Well". A Closed XML system is one where a single party creates and uses the XML documents. Certainly this happens all of the time. We all create little XML documents with one-off throw-away models for one task or another that only we use. These documents will not be the focus here. When documents are created in a closed XML workflow and sent to another entity - such as an archive - for reuse, publishers can quickly learn that the content they have been accumulating is not useful for anything outside of their system and may not be useful if their own systems are upgraded or changed.