Resources / Examples of Marking up a Periodical in TEI? « Digital Humanities Questions & Answers

Digital Humanities Questions & Answers » Applications, Tools, Formats

Resources / Examples of Marking up a Periodical in TEI?

(7 posts) (5 voices)

Asked 4 years ago by cforster
Latest answer from Laura Weakly
This question has a best answer.

Tags:

cforster
Member
I am interested in projects that have used (relatively light) structural TEI to markup issues of a periodical. There isn't an example of such a case in the excellent TEI by Example site nor could I find nice documentation elsewhere.

Chiefly I'd like to be able to markup individual items within each issue so that a query could return all material by one author, or a list of all items which are "reviews" or "prose" or "poetry" and so on. When I tried to figure out the best way to markup a table of contents for a single issue of a periodical, for example, I wasn't able to find too many resources (largely, I think, b/c my google-fu failed; the query "TEI 'table of contents'" returns, predictably, lots of TEI documentation which itself has a table of contents).

Any suggestions or guidance for readings would be very welcome.
Tweet this question
Posted 4 years ago Permalink
mdalmau
Member

At Indiana University, we encoded following the TEI P4 Guidelines, our first scholarly journal, The Indiana Magazine of History (IMH, http://www.dlib.indiana.edu/collections/imh/) back in 2008. The journal is encoded at the issue-level with article-level bibliographic metadata stored in independent headers, which we use for querying author, title, etc. Since we encode at the issue level, article types are designated in the divs (e.g., reviews) and are used as search filters. The site makes available an "on-the-fly" TEI file at the article level. If you'd like to see what our issue-level encoding looks like, email me (mdalmau@indiana.edu) and I'll send you a file.

You can find some basic information about our encoding approaches on the web site (http://webapp1.dlib.indiana.edu/imh/projectInfo/encoding.do), but because my colleagues and I, like you, found very little guidance for how to best model the markup for serials for which we wanted both browseable issue-level access and searchable article-level access, two of us published an article that includes greater detail of our encoding practice and discovery mechanisms:

Dalmau, Michelle and Melanie Schlosser. "Challenges of Serials Text Encoding in the Spirit of Scholarly Communication." Library Hi Tech 28. 3 (2010): 345-359.

I could also share with you our internal IMH encoding guidelines, but they are not for the faint-hearted.

Posted 4 years ago Permalink
Laura Weakly
Member
Best Answer

We are working on an online project at the CDRH for Every Week Magazine and are very interested in the questions you are asking. Currently we have about 74 issues that we have encoded and will be ready for a launch in the near future. Please note that we are still in the process of making changes, but you may look at the prototype here:

http://libxml1a.unl.edu:8080/everyweek/search?browse-all=yes

I would be happy to share our encoding if you are interested and discuss the problems we have encountered. In the future, we plan on exposing our TEI but haven't done so yet.

Posted 4 years ago Permalink
CLKCrompton
Member
Best Answer

I'm the former project manager for a site devoted to fin-de-siècle periodicals, The Yellow Nineties Online (http://www.1890s.ca). The TEI for our reviews, poetry, essays, and indeed all content, is up on the site (although I will warn you away from volume one of The Yellow Book - it was our tester volume, and is marked up with some tags that we don't use anymore). There are a few essays on our process in the About section of the site. We're still working our how to leverage our TEI for search purposes - the Yellow Nineties team will have an essay up about it in the coming year, I imagine.

Posted 4 years ago Permalink
Kevin Hawkins
Member

Replying to @cforster's post:

One approach is to create a TEI document for each article. You can then easily attach metadata to each article using the teiHeader. You would need to come up with a way to tie together the articles in an issue. There are various approaches here, some using TEI and some using an outside method like METS.

As for encoding a table of contents, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/DS.html#DSFRONT , which discusses use of type="contents" on a div. As explained here, this div would contain a <list> (which would contain an <item> for each entry in the TOC).

Posted 4 years ago Permalink
cforster
Member

Thanks very much all for your help.

@mdalmau: Appreciate the references. I'll definitely check them out.

@kevin: It had occurred to me that each article could be encoded separately; my sense is, for my purposes, this might introduce more work in trying to stitch everything together. Such stitching (across issues or even across different periodical titles) is, at some level, unavoidable. I'm not sure I sufficiently understand the costs/benefits though to know what's preferable. I imagine exactly how one is performing that "stitching" would be a key component.

@laura: Thanks for the link; the site looks great. If you wouldn't mind sharing an example of your raw XML (and maybe Schema) I'd love to have a look.

@CLKCrompton: Thanks for the link; this is a great model (and thanks for the heads up about Vol. 1); and it is really great that you make the raw XML available (seems rare). Both 1890s online and Laura's "Every Week" are excellent models for what I'm interested in.

Many thanks folks!

Posted 4 years ago Permalink
Laura Weakly
Member

Replying to @cforster's post:

FYI: Every Week went live today at its permanent URL http://everyweek.unl.edu

Posted 4 years ago Permalink

RSS feed for this topic

Reply

You must log in to post.