Identify centres that are nodes in more than one RI

[bansp]

Find out which centres double as CLARIN / Text+ (/DARIAH) centres, to see how the information can be packed and visualised.

The RI column becomes relevant in this regard, and also the display of info on individual centres.

[margaretha]

Since this issue concerns multiple functions, I am breaking it down:

1. Presenting RI in the centre info page

How about listing the RI as shown below:

Research Infrastructure:
   * CLARIN (B-centre)
   * Text+

The attribute status is required within ri in the scheme. Do other RI have statuses?

2. Presenting RI in the centre list

Since RI and status must correspond to each to other, would it be better to get rid of the status column and include the status inside brackets like in the centre info page?

Research Infrastructure
CLARIN (B-centre)
Text+

3. Filtering the centre list

How about using a multiple drop down form to filter centres with multiple RIs?

[bansp]

Going in reverse order:
3. "How about using a multiple drop down form to filter centres with multiple RIs?"

I am not sure what that means, let's talk about it on Tuesday. Intuitively, I would think that a Text+-oriented user might want to set their Text+-orientation once and expect not to be bothered with filtering other RIs out with every search.

2. Sounds great to me.

3. (1.) Good question about whether the attribute should be mandatory; I tend to think at the moment that perhaps it should, but with an option to set it to the null string. In Text+, they have data domains: https://www.text-plus.org/en/research-data/data-domains/, so a centre can be in Collections, Lexical Resources, or Editions (sometimes in more than one, like the IDS).

[margaretha]

I have updated the RI view on the centre page and list in 2122dc8

[bansp]

There is a nice complication here: BAS is a centre in CLARIN, but it's identified as LMU in Text+. LMU stands for Ludwig-Maximilians-University and that's the easy part. It's worse if a centre has "CLARIN" in the name and works also for another network, where it is identified by a different name (and perhaps has even a different legal identity). We need some clever solution:

• either a @preffered-name attribute inside <ri> -- but that will only suffice for (say) the short name, and the long name will remain unchanged, which is not ideal
• or a separate <centre> with a @sameAs attribute that points to an @xml:id.
• or... ?

For mid-May 2023, I will not address this.

[bansp]

This issue is ready to be closed, I believe.

[bansp]

Closing, but keeping a link to the comment posted on May 16th, because that is still an open issue (albeit a separate one).