Update request for Sensitive data page

[pinarpink]

This page addresses the topic of detemining and reducing data sensitivity. we can consider renaming the page from "Sensitive data" to "Data sensitivity" to better reflect page content.

This page lists in the tools section to several tools, mostly frameworks and environments to host and process sensitive data. The listing is due to the "sensitive data" markup on tools in the tools tabke. the page text makes to reference to any of the tools. so I'd suggest for each tool

• either the solutions sections should be updated to add a references to tools and mention how it can be used to manage data sensitivity.
• or If a listed tool is not relevant to detemining and reducing data sensitivity then the tool's link to this page shall be removed.

For the following two tools:

• ELIXIR AAI is currently listed, which is not a relevant tool as this page is not about TREs or Infosec. AAI needs to either be linked to the Human Data page where infosec is mentioned, or it should be linked to the dedicated Infosec page, which will be written.
• nettskjema looks like a national resource and shoul dbe marked accordingly.

[pinarpink]

@rwwh would you approve the renaming of the "Sensitive data" page as "Data sensitivity"?

[rwwh]

I have no fundamental problem with the naming. However note three things:

1. The page is under "your task" and "data sensitivity" is not the name of a task. This is the same for many other pages in this section: "Data protection" can be a task/responsibility, but "Data management plan" is a thing.
2. Naming all of the task pages "Data x" and listing them alphabetically under "D" is a bit weird.
3. Any renaming of pages is accompanied by an appropriate "redirect"?

[pinarpink]

• Indeed page naming is inconsistent. We also considered "Data sensitivity classification" or "Data classification". How ebout these, or do you have a suggested name?
• The issue with the page at the moment is that the text and the tools table are out of synch. There is no reference to any tool in the text, whereas the tools table has a long lists of tools, those that have been tagged by their providers with the page tag "sensitive_data". And only one of these tools appear to be related to the activities of determining and reducing data sensitivity.
• The URL will not change, Bert tells us, so a redirect is not needed

[rwwh]

If it called anything like "Data Classification" the index becomes useless: nobody will look for content about sensitive data under that name, and there are so many other forms of classification that are not sensitivity-related and not mentioned on that page.

I'm not dealing with tools list: this is probably a typical "specialist" vs "compatible" issue. Is your supermarket listed under "eggs" in the yellow pages? Nope. Similarly, we have to decide whether the tag "sensitive data" (as example) should be attached to any tool that can deal with sensitive data (i.e. all those that are not incompatible with it), or only to tools that perform specialized services for sensitive data.

[pinarpink]

Thank you Rob. Let's go for "Data sensitivity". An outcome of the recent hackathon is a feature that allows referring to tools from within text in a manner that the site theme understands; tag-based linking of tools to pages and the automatic tool listings will disappear.

[bedroesb]

@elixir-europe/rdmkit-editors, do we change Sensitive data to Data sensitivity?