leidenuniversitylibrary / cds-lab-homepage Goto Github PK

The "working with data" guides are more or less categorised by activity. If we want to fit them within a framework of activities, we could link them to the TaDiRAH. Only for the things that make sense, of course. I don't understand why "DOI" would be included in a classification of research activities.

The IIIF portal will no longer exist after the iiif domain moves.

It would be great if some server automatically builds and tests the website when the git repository is updated. Since the repository is currently private, we cannot use the free Travis-CI.

Testing could include spell checking and link checking, as well as checking semantic markup and licensing information.

Storing the built files is another question: we could store them in a special branch that is force-pushed to overwrite on every build or use rsync to save the HTML and assets outside the build environment (this could be combined with deployment, but I would like to separate the issues).

The KNAW released Loghi, an application for hand-written text recognition. This may be a useful alternative or addition to Kraken, Transkribus and eScriptorium.

The homepage of the lab server is currently the most important index of projects. The reason for putting projects on the homepage was their visibility, but I feel that this overview starts to grow too large. We should keep this list concise. We could use headings for the kinds of projects we do, list some examples and refer to the (more) complete separate project index and pages for individual projects.