-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify a manifest format #230
Comments
As we discussed earlier, I tested this at several occasions and implemented it in the client: Some examples (sorry, copied from various sources): For the original "VeBiDraCor" that was used in the "Small World Paper" I used this notebook https://github.com/dracor-org/vebidracor/blob/main/vebidracor-workflow.ipynb
I reworked that to the manifest format currently used in the stable-dracor-client:
You could also look at the manifest of the capek drama corpus here: https://github.com/ingoboerner/stable-dracor/blob/capek/capek.ipynb
An example of the manifest of VeBiDraCor created with the "client":
A corpus created from multiple sources:
here: https://github.com/ingoboerner/stable-dracor/blob/develop/test_client.ipynb Serialized as Docker image labels:
|
In order to populate a dracor-api instance with a defined set of documents and corpora we want to design a file format that describes the contents of the DraCor instance. This format should support the following use cases:
The text was updated successfully, but these errors were encountered: