Create New Entry

Create a new record

You shall now find a new "create new entity" function in the navigation bar of the app. You only need to enter the name of the file, for manuscripts this is the full filename, for the other entities just the last (not numerical) part of the ID (see <TEI> schema specification). For LIT1234iliad, you would enter only "iliad". For a manuscript, simply enter the full name, the small print will indicate you what is needed. As you start typing the button will become active and you can create the file. This is stored in the app, not in Github! As the confirmation page will tell you blinking, you need to

  1. download the file
  2. save it in a folder called "new" into the proper folder
  3. commit and sync to git
Once you have done this GIT and our server will be again in sync, which means you can now move your file if you need to (especially for manuscripts) and then commit and sync this change again.

If you omit the first step, we will have two identical files in two locations and thus the ID lookup of the app will fail not showing you your file. On leaving the page you will get a warning every time, intended to make you stop before you carry on without syncing. The generated file will have a consistent new ID and will insert it in the appropriate place in the file. This should avoid the really frequent problem of IDs not being updated after copy-pasting a master file. It remains entirely possible to create your files in oXygen as previously, but the application interface is recommended as it makes sure your ID is unique. The file will also have the correct type and a <change> element with your initials and current date.

Especially when creating a new work record, where the numerical part of the ID will become the Clavis reference number, only the app should be used.

Check the principles for creating a WORK entity and the page about how to decide between a place and an institution record.

To decide whether to create a new place record or not if in doubt, try the following.

  1. check if there is a record already in our list
  2. if yes, then
    1. check if there is also a wikidata item (you can simply google what you are looking for, open the correct wikipedia page you find and hit the wikidata item link on the left).
      1. if yes add a @sameAs attribute with the Q ID in the URL or at the top of the item.
    2. check if there is also a record in geonames.org
      1. if yes add a @sameAs attribute to place linking to such geonames ID.
      2. if not leave the record
  3. add a ref to our record
  4. if not, then
  5. check if there is also a wikidata item
  6. check if it is in geonames.org
  7. if yes add the uri in the @ref
  8. if not (but check thoroughly, because it would be an exception) create a new place record

Generally, when possible it is always preferable to have an external link to an authority file for places out of scope which we are not going to describe or give details about. If there is already a record, no need to delete it or update it. Simply add the Wikidata Entity.

Adding references to places not in our db:

  1. for ancient place prefer pleiades, with namespace pleiades
  2. for places related to the Coptic literary tradition use PAThs

This page is referred to in the following pages

Revisions of this page

  • Pietro Maria Liuzzo on 2018-04-30: first version of guidelines from Wiki