musdb
- Basic re-implementation of separated measurements for objects (tab: “addendum”)
- The type of measurement (width, length, etc.) is now managed using a controlled list, which can easily be extended. This also allows for measurement types of different levels of specificity (“width” vs. “width of socle”)
- The new implementation allows users to identify whether a measurement is exact and add notes for each measurement
- Measured values now need to be entered as a floating point number – consistent search for objects smaller or larger than a given size is thus made possible (previously only available for entries where the system could deduce a numeric value from whatever had been entered)
- Unique naming components of entered tags are automatically parsed into a relation type. German: “Apfel (Motiv)” is automatically split into the tag “Apple” and the relation type “display subject”.
- Users entering a tag with such a naming component that is known to belong to another vocabulary will have their input auto-corrected to reflect both. Entering the tag “Berlin (Motiv)” will be auto-corrected to a link to a “displayed place” “Berlin”.
- The list of spaces that can be linked to an object as its current location is now sorted alphabetically
Frontend
- Re-implemented separated Measurements
Import
- The import tool now also uses the new implementation of separated measurements
- Unique naming components of entered tags are automatically parsed into a relation type. German: “Apfel (Motiv)” is automatically split into the tag “Apple” and the relation type “display subject”.
- Users entering a tag with such a naming component that is known to belong to another vocabulary will have their input auto-corrected to reflect both. Entering the tag “Berlin (Motiv)” will be auto-corrected to a link to a “displayed place” “Berlin”.
- Links between two objects are now imported using the dedicated data type for this purpose. They had previously been imported as regular web links.
nodac
- When merging two entries, links between the entries and collections, exhibitions, etc. are now reflected and rewritten
- previously, links to such data types prevented the completion of the merge
- If an entry’s name is marked to always belong to e.g. a tag, the buttons for transferring the entry to the actor, place, or time vocabularies are now hidden.
- If an entry is moved between vocabularies, links between the entry and objects as “display subject” / “displayed place” / “displayed actor” are reflected and translated into new links using the appropriate link type.
- A new context menu on overview pages allows for a quick access to functionalities like the splitting of entries
