Export document by professional key
- At the moment, a flatdb document is only exportable by primary key
- or by the deprecated method
getDDIStore
which uses the deprecated and wrong server rest endpoint/ddistore/{study}
- What is the problem from my point of view?
-
study
aliasdocumentIdentifier
is not the correct professional key - I think
documentIdentifier
anddialectDefinitionName
identifies a document
-
- Endpoint on server-side must be provided before
Discussion
- Use cases
- Split same document with same
documentIdentifier
but different dialect definitions -> not probable - Split different documents with same
documentIdentifier
and different dialect definitions -> ED-Indexing Flatdb instance consolidation (CBE-DDI31)
- Split same document with same
- Decision: Tupel
documentIdentifier
anddialectDefinitionName
form professional key
Edited by Alexander Mühlbauer