Custom Query (13 matches)
Results (1 - 3 of 13)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #16 | fixed | Calendar certainty | ||
| Description |
Jamil / Sally (19.12.2010) if a converted date into CE does not contain all the dating information—day of week, month, day, year—it will not be saved. But we need a way to save dates in different types of format. For example, 1290 H which could fall in either 1873 CE or 1874 CE. Can this be done with the current fields, or do we need to create different fields for these type of date entries? 6b) also if a non-numerical character is put in the year field, the entity will not be saved: e.g. ca. 1114 H. not only does not get save; the entire entry for the witness is also lost |
|||
| #1 | fixed | Method to validate the consistency of the codex | ||
| Description |
Method to validate the consistency of the codex in the Witness form. The method should have the following behavior: •If the collection selected is “No Collection”, the identifier (Shelf Mark) of the correct can be repeated by more than one codex. •Else, the codex’s identifier should be unique. |
|||
| #3 | fixed | Unique code identifier | ||
| Description |
In Codex from, by saving we must ensure that the combination Country-City-Repository-Collection-Codex.identifier is unique in the DB (despite if the Collection is the “No collection”). |
|||
