The Textual Communities API

One of the core aims of Textual Communities is to make it possible for people with limited programming skills to make their own web pages offering an interface to their own materials in the TC system.  We do this through an "API": an Application Programmer's Interface. In essence, this is a series of calls to the TC database to bring back data: the XML for the transcription of any page, or any entity, in your community.

Here are the basic calls you need: brings us back a list of communities in the USask system

from this we learn that this Matthews diary is community 91, and gives information about it tells us all the documents in this community -- there are two, the first one, with id 1497295, is the War Diary. tells us more about the War Diary document lists all the pages in the Ware Diary document; for example id 1497299 is folio 4 gives us the xml for this page, folio 4 of the War Diary  tells us all the entities in this community (ie, all the diary entries), eg 620366  is May 25th 1846 tells us the paragraphs in this entity (three of them) tells us what texts there are of this diary entry (only one, with the id 3006519) gives us the xml for the whole of this diary entry in the document 1846, all through paras (could be a pb in this page, actually there isn't) 

Perhaps the most powerful and distinctive feature of TC is its ability to mix calls concerning documents and entities: asking, for example, exactly what entities are in what document, and in each page of that document, or in what documents and in what pages of those documents particularly entities are to be found.  Thus: tells us what entities are in the War Diary tells us what entities are on folio 4 of the War Diary (the entries for May 24, 25 and 26). 

There is a sample file using some of these calls at  The code for this file is at

0 Attachments
Average (0 Votes)
No comments yet. Be the first.