Decide on a consistent scheme for the xml:id
#53
Comments
|
Yes, I think so, with the usual caveat to check and allow for how this might impacts files which are derived from / shared with external aggregators (i.e. I'm thinking primarily of FIHRIST in this instance). |
|
Branwen has also flagged Fihrist as an issue; so what if we enforced consistency for everything except Fihrist? (And even there, we can do some validation that, e.g., the same ID hasn't been used twice.) |
|
Thank you everybody! This sounds like a great plan, Alex. The only instance of external aggregators is indeed Fihrist (which essentially means the Arabic files plus whatever goes in the Fihrist folder of stuff that is not to go on the front end). Others might come in the future, but, as you say, this is only something we would look into with the platform team's input. |
At the top of every TEI file is a
<TEI>element with anxml:id, e.g.Currently they're a bit of an inconsistent mess:
List of all
xml:idvaluesNow we've made the display labels consistent, would it be useful to make these identifiers consistent also? e.g.
MS_$language_$number. That's something we could add to the XML checker.It would have caught a recent error – both
MS_Hebrew_B_5.xmlandMS_Hebrew_B_6.xmlhad the samexml:idvalue, which was causing conflicts.Note: please don't change these IDs without talking to the platform team first. We'll need to do some work on our side to make sure existing URLs to manuscripts don't change when these IDs change. It's possible, we just need to schedule it.
The text was updated successfully, but these errors were encountered: