b7d7c15407
add mapping from objectToObjectLinkSet to lido:relatedWork, includig lido:displayObject and lido:objectWebResource
2026-02-20 18:18:11 +01:00
06edc8ac8c
add check for empty element (literatur_isbn, literatur_gnd) to avoid creation of empty LIDO element
2026-02-20 18:15:15 +01:00
6f17a9c81d
update mapping literature_online from lido:objectID to lido:objectWebResource
2026-02-20 18:09:47 +01:00
689337f86f
Merge branch 'master' of gitea:museum-digital/musdb-md-xm-xsls
2026-01-04 00:27:43 +01:00
43baf36c87
Replace hard-coded type for collections from "Sammlung" to "Collection"
2026-01-04 00:22:20 +01:00
6cb0e45536
add type attribute to recordInfoSet and recordMetadataDate #13
2025-12-15 17:42:20 +01:00
6a8c98920f
Reflect collection-level ISIL IDs in md:xml export
...
Close #1395
2025-10-31 15:04:04 +01:00
d54dbe278b
Use ISO dates for start / end
2025-10-31 14:44:56 +01:00
a3973c5c62
fixed unnecessary linebreaks after '(?)' in lido-1.0
2024-11-08 13:10:57 +01:00
73e749160c
Changed lido:resourceRepresentation@lido:type for pdf from 'text' to 'provided_text' for DDB compatibilityMerge remote-tracking branch 'upstream/master'
2024-10-02 17:47:55 +02:00
6c2b829daa
changed lido:resourceRepresentation@lido:type for pdf from 'text' to 'provided_text' for DDB compatibility
2024-10-02 17:06:15 +02:00
c9c7b63434
Display objectWorkType via tags in EODEM and LIDO 1.1 exports, and only
...
that in case both object_type tags exist and an object type is present
in md
See #5
Background for the disabling of exports of the regular object type in
case both exist: The German Digital Library (DDB) is unable to handle
duplicate names in work types unless both contain different links to
norm data repositories. This fix allows the DDB to more easily import
while supposedly not losing meaningful data.
2023-08-03 23:11:08 +02:00
2ff939c6db
Cover controlled terms for objectWorkType and material / tech in LIDO
...
1.0 exports
2023-07-09 22:18:25 +02:00
a32d94a2f5
fixed xsi:schemaLocation
...
Currently, the export generates (erroneously, I guess) an `xmlns:schemaLocation` namespace and consequently doesn't link the gml schema properly. I've changed the attributes in `lido:lidoWrap` to fix this issue.
Signed-off-by: Alexander Winkler <winkler@zib.de >
2023-02-28 17:18:51 +01:00
6410a5bdb5
Fix references to position in literature in LIDO-based XSL files
2023-02-28 14:11:46 +01:00
d9fe60d541
Add XSDs for validating exports and an (almost) complete EODEM export
2023-01-08 22:58:17 +01:00
e77e7ff96f
Improve portrayal of uncertainty in lido 1.0
2022-08-01 03:56:18 +02:00
cb3b22ba36
Replace language-specific lines in LIDO 1.0
2022-07-27 17:33:52 +02:00
f5c34f51b7
Initial.
2022-07-15 17:33:19 +02:00
