You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the mark-up indicating the type of a document varies from type to type.
In the "old" VICAV headers, we don't have any indicator at all, or - like in TUNOCENT - use this structure (invalid BTW):
@dasch124 TUNOCENT only uses these categories at one place on BaseX side. I pushed a PR that modifies that part of the code and will push the correponding changes to vicav-vue repo as well.
The other place, the old logic for generating dat lists are not used in vicav vue any more.
@dasch124 TUNOCENT only uses these categories at one place on BaseX side. I pushed a PR that modifies that part of the code and will push the correponding changes to vicav-vue repo as well. The other place, the old logic for generating dat lists are not used in vicav vue any more.
That would be me. We're currently working on harmonizing the WIBARAB data structure anyway, if/when we adapt the TUNOCENT format, I'll adjust the query if necessary
Currently, the mark-up indicating the type of a document varies from type to type.
In the "old" VICAV headers, we don't have any indicator at all, or - like in TUNOCENT - use this structure (invalid BTW):
I'd like to harmonize this to the format we use in the TUNOCENT corpus documents, i.e.
Would changing this in the data break things in the back-end?
The text was updated successfully, but these errors were encountered: