This repository has been archived by the owner on Nov 24, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
Move dataset descriptions to YAML #324
Comments
Duly noted (I agree, BTW). We'll redesign the website in the coming months. May we come back to you and ask to review the concept? |
Sure, I'd like to have a look!
Am 14. April 2018 21:35:03 MESZ schrieb gitstief <notifications@github.com>:
…Duly noted (I agree, BTW). We'll redesign the website in the coming
months. May we come back to you and ask to review the concept?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#324 (comment)
--
Jakob Voß via Android
|
Whats the current state of this issue? Is there already a script able to parse the daten/index.html? |
There won't be a daten/index.html, since we'll be moving codingdavinci.de to a Drupal-based solution. I'll refer you @lucyWMDE for more information. |
I already talked to Lucy – my question here was only about the technical aspects of the data migration. Or is somebody manually transfering the data per c&p into the Drupal instance? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Individual dataset descriptions should better be expressed in YAML instead of /daten/index.html. HTML view can then be generated from YAML source. In a second step the data view could be modified to get stable URIs for each dataset. Another idea is to add authority identifier, links with Wikidata etc. but having the descriptions in YAML is the first step.
The text was updated successfully, but these errors were encountered: