-
Notifications
You must be signed in to change notification settings - Fork 3
Lessons learned
Adrian edited this page May 29, 2019
·
1 revision
Adrian gave a talk about the SkoHub project in the hbz's English class. The slides at http://slides.lobid.org/skohub-hbz/ were quickly prepared just before the session based on the blog post. Here are some lessons learned:
- Bad choice of example: the example use case, the choice of "Environment" as subject caused some confusion as one participant thought this referred to a "SkoHub environment" for subscription and updates.
- Making clear the focus is not on upgrading repos but web content: As I outlined the repository approach in the beginning, people thought that SkoHub would be an improvement for this approach. I think it is rather a complementary approach. While you might use SkoHub for OA repositories, I guess the infrastructure there is already functioning ok (as you have an exclusive group of people you can identify and address to publish their stuff in OA repositories). SkoHub is rather good for addressing all the resources that are scattered around the web and have not been recorded yet or collected in search indexes.
-
From the concrete to the general: Rather than describing the abstract approach (slides 13 to 19 and then giving a concrete example, one should start with a concrete problem and then going to the general infrastructure.
- This also applies to the fact that SkoHub can be used on very different authority data (e.g. big authority files like GND or small classifications like ISCED-2013 or the whole Wikidata etc.) and with very different publications (OA articles, OER like work-sheets or presentation slides, openly licensed images etc.). One should highlight this general applicability in the end but focus on a concrete use case throughout the presentation. And OER is probably a very good example.
- Demos: we need UIs to demo
- Pick up "off the web": As "off the web" is used in slide 10, this should be picked up in a later slide with "of the web"