- ab
- abbr
- acquisition
- add
- additional
- additions
- antiphon
- app
- bibl
- binding
- bindingDesc
- catDesc
- category
- cb
- Certainty
- change
- choice
- cit
- citedRange
- collation
- collection
- colophon
- condition
- country
- creation
- custEvent
- date
- decoDesc
- decoNote
- del
- depth
- desc
- dim
- dimensions
- div
- editor
- ex
- expan
- explicit
- facsimile
- faith
- filiation
- foliation
- foreign
- gap
- geo
- graphic
- keywords
- handDesc
- handNote
- handShift
- height
- hi
- history
- idno
- incipit
- item
- l
- language
- layout
- layoutDesc
- lb
- lem
- list
- listApp
- listBibl
- listPerson
- listRelation
- listWit
- locus
- material
- measure
- msContents
- msDesc
- msIdentifier
- msItem
- msFrag
- msPart
- nationality
- notatedMusic
- note
- objectDesc
- occupation
- orig
- origDate
- origin
- origPlace
- p
- pb
- persName
- person
- personGrp
- physDesc
- place
- placeName
- provenance
- ptr
- q
- quote
- rdg
- ref
- region
- relation
- repository
- roleName
- rubric
- seal
- sealDesc
- seg
- settlement
- signatures
- source
- space
- subst
- summary
- supportDesc
- supplied
- surrogates
- TEI
- term
- textLang
- title
- unclear
- watermark
- width
- witness
- active
- ana
- assertedValue
- atLeast
- atMost
- cRef
- calendar
- cause
- cert
- color
- columns
- contemporary
- corresp
- defective
- dur
- evidence
- facs
- form
- from
- hand
- href
- ident
- key
- n
- name
- new
- notAfter
- notAfter-custom
- notBefore
- notBefore-custom
- part
- passive
- pastedown
- place
- reason
- ref
- rend
- rendition
- resp
- role
- sameAs
- script
- source
- subtype
- target
- to
- type
- unit
- url
- value
- when
- when-custom
- who
- wit
- writtenLines
- xml:base
- xml:id
- xml:lang
- @source
- Additional
- Additions and Varia
- Aligning transliteration and morphological annotations with Alpheios Alignment Tool
- Art Themes
- Attribution of single statements
- Authority files (keywords)
- Bibliographic References
- Binding Description
- Canonicalized TEI
- Catalogue Workflow
- Collation
- Colophons, Titles and Supplications
- Contributing sets of images to the research environment
- Contributing to the research environment
- Corpora
- Create New Entry
- Create a new file, delete existing, deal with doublets
- Critical Apparatus
- Critical Edition Workflow
- Dates
- Decoration Description
- Definition of Works, Textparts and Narrative Units
- Documentary Texts
- Dubious spelling
- Editing the Schema
- Editing these Guidelines
- Editions in Work Records
- Entities ID structure
- Event
- Figures and Links to Images
- General
- General Structure of Work Records
- Groups
- Hands Description
- History
- Identifiers Structure
- Images
- Images of Manuscripts for editions
- Inscriptions
- Keywords
- La Syntaxe du Codex
- Language
- Layout
- Letters
- Linking from Wikidata to the research environment
- Manuscript Contents
- Manuscript Description
- Manuscript Physical Description
- Manuscripts
- Named Entities
- Narrative Units
- Object Description
- Person
- Place or Repository
- Places
- References
- References to a text and its structure
- Referencing parts of the manuscript
- Relations
- Relative Location
- Repositories
- Revisions
- Roles and roleNames
- Scrolls
- Seals Description
- Setup
- Some useful how-to for personal workspace set up
- Spaces
- Stand-off annotations with Hypothes.is
- Standardisation of transcription from Encyclopaedia Aethiopica
- State and Certainty
- Statements about persons
- Structure
- Summary on the Use of @ref and @corresp
- TEI
- Taxonomy
- Team IDs
- Text Encoding
- Training Materials
- Transcriptions with Transkribus
- Transformation
- Transliteration Principles
- Users
- Using Xinclude
- Validation process
- Workflow
- Works
- Works Description
- Zotero Bibliography Guidelines
- titleStmt of Manuscript Records
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 (non-numerical) part of the ID (see
<TEI>
↗ schema specification). For LIT1234iliad, you would enter only
"iliad". The non-numerical part of the ID may not exceed 15 digits and may only include ASCII symbols.
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
- download the file
- save it in a folder called "new" into the proper folder
- commit and sync to git
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 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 a repository record.
To decide whether to create a new place record or not if in doubt, try the following.
- check if there is a record already in our list
- if yes, then
- 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).
-
- if yes add a
@sameAs
attribute with the Q-ID in the URL or at the top of the item.
- if yes add a
- check if there is also a record in geonames.org
-
- if yes add a
@sameAs
attribute to place linking to such geonames ID. - if not leave the record
- if yes add a
- add a ref to our record
- if not, then
- check if there is also a Wikidata item
- check if it is in geonames.org
- if yes add the URI in the
@ref
- 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 database:
- for ancient place prefer Pleiades, with namespace Pleiades
- 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