Generic Programmable Corpora (dracor-frontend) based on DTS API

[ingoboerner]

We could transform the existing EcoCor front end (or a front end based on DraCor React,...) into a more generic GUI that utilizes the DTS API to display the contents of Programmable Corpora via DTS.

A basic version could include:

• Displaying Collections (=Corpora) as cards on the landing page: The data would come from the DTS Collections endpoint, e.g. DraCor DTS API (https://staging.dracor.org/api/v1/dts/collection).
• This could use the extensions property of the Collection Objects (currently not implemented in the DraCor DTS on collection level). We could either define some general features of Programmable Corpora (for reference on metadata of corpora see also the poster: https://zenodo.org/records/11202132 and the underlying survey) and make them mandatory (e.g. a token count); or, which would be the more elegant version, let implementers decide what to put there (this would need some kind of configuration file)
• Showing Corpus Content in a Table Format: or each corpus, such as the one available at https://staging.dracor.org/api/v1/dts/collection?id=ger, we could display the contents in a table format similar to what's seen on https://ecocor.org/corpora/de
• View of individual text: Metadata on a single text could come from the Collection endpoint: https://staging.dracor.org/api/v1/dts/collection?id=ger000640 see property extensions and the Navigation endpoint https://staging.dracor.org/api/v1/dts/navigation?resource=ger000640&down=-1
• Use as basic text rendering using CETEIcean based on the TEI-XML data retrieved from the DTS Document endpoint, e.g. https://staging.dracor.org/api/v1/dts/document?resource=ger000640
• Sending to generic external tools (Tools Tab), e.g. Voyant, CLARIN Language Resource Switchboard, ...
• Additionally, we might consider adding a download option (Tab) for TEI and/or text views, accessible via https://staging.dracor.org/api/v1/dts/document?resource=ger000008&ref=body/div[1]&mediaType=text/plain .

The primary modification would likely involve adapting the front-end function that builds the cards on the homepage. The relevant code can be found here: https://github.com/EcoCor/ecocor-frontend/blob/main/src/api.ts#L31-L41

One of the key goals would be a front end that supports DraCor-like API functionalities, but based on a generic API (=DTS) by leveraging the extensions capabilities of DTS Collection and Resource Objects. These can hold project specific custom metadata (as linked data, because JSON-LD...)

[ingoboerner]

ping @mromanello ;)