two kinds of centre description pages at clarin.eu -- link to both...

[bansp]

(It is so nice to only learn about such things from the CLARIN newsletter. Still...)

There now exist two ways to point at centre information. Take ARCHE:

• centre registry: https://centres.clarin.eu/centre/45

• persistent handle at clarin.eu: http://hdl.handle.net/11372/DOC-105

We only use the former, but should probably also use the latter, the more so that the former doesn't point to the latter (and ain't that somewhat weird, huh).

(SIS) https://standards.clarin.eu/sis/views/view-centre.xq?id=ACDH-ARCHE

Task: add one more element to handle the more descriptive links.

(Subtask: ask why wouldn't those pages reference the centre recommendations provided by the SIS, as above.)

[dietervu]

Quick follow-up for clarification:

• the handles only exist for certified centres
• the shorthands (specified in centre registry) are used to generate the clarin.eu pages, eg https://www.clarin.eu/centres/acdh-ch-arche
• adding a link from the website or centre registry to the SiS either needs to be done manually (not ideal, error-prone) or automatically, but then we need a call or so to know if the centre exists in the SiS using the shorthand as parameter -- even then I cannot guarantee that with the current setup we can easily add this

Overall, we are in a huge operation transitioning towards automated synchronisation between the centre registry and the website. As always the bottleneck are procedures and human workflows. At this stage I would be very careful adding more complexity.

[bansp]

Thanks, Dieter!

What could be done, on the side of the SIS, is:

• store the registry shorthands (we modify them if a centre requests a modification, e.g. CLARINSI got turned into CLARIN.SI)
• use them to point to clarin.eu space, with something akin to concatenate('https://www.clarin.eu/centres/' , translate(lower-case($shorthand),' ','-')) , if I get the idea right (although then, we wouldn't use the handle.net handles, which seems a bit of a pity)
• use them also to provide a mapping for external API calls by original shorthands, basically returning https://standards.clarin.eu/sis/views/view-centre.xq?id=CLARIN.SI if the API is asked for shorthand=clarinsi .

Naturally, it would indeed be a bit of added complexity on the side of the SIS, and also on the side of the core infrastructure, which would want to check if id=clarinsi returns a non-zero string before providing the link returned by the API. I realise that I won't be able to talk you into trying that on the spot, so I just signal willingness to handle this on the SIS side, if you decide to greenlight the above (or a similar) solution, at some point.