Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a dataset shopper, I want to see certain information about a dataset on its page, so that I know how I can use it #81

Open
12 of 17 tasks
mwigham opened this issue Feb 1, 2024 · 6 comments
Assignees

Comments

@mwigham
Copy link
Contributor

mwigham commented Feb 1, 2024

The following information should be displayed on the dataset page, where applicable:

  • Links to available tools (e.g. Media Suite)
  • Dataset description
  • Links to available APIs (e.g. Analysis API)
  • Links to NDE/Clariah registers
  • Links to any data downloads
  • Link to the dataset on the SPARQL endpoint
  • Link to the Linked Data schema

Comment moved from this issue:
"Consideration: improve presentation of LOD info of dataset on the dataportal page. To make it clear there is LOD for a dataset. E.g. don't put it on a tab, also consider logo/colors for infobox."

Tasks:

  • Get user feedback (René) as to the desired location of this information (e.g. Description, Metadata...?)
  • Determine where to store the information (spreadsheet, dataset description in register...?)
  • Design a new layout for the page
  • Add the information for the MOZ
  • Display the information on the MOZ page - just in markdown
  • Review with team, adjust
  • Work out how best to display the information, implement this
  • Review with René
  • Add the information used in the final version to the MOZ document in the datasets folder, and update the README to encourage adding this information

Acceptance criteria:

  • The desired information is shown on the MOZ page
@mwigham
Copy link
Contributor Author

mwigham commented Feb 2, 2024

Roosmarijn checked with NDE about whether we can add our own fields:

"Als dataset publisher staat het je vrij om extra schema.org properties op te nemen in datasetbeschrijvingen. Maar het Datasetregister harvest en toont deze inderdaad niet. Daarvoor moet een property toegevoegd worden aan https://netwerk-digitaal-erfgoed.github.io/requirements-datasets/ (waarna ook de crawler/converter en SHACL aangepast moeten worden). Dit kan door het opvoeren van een issue in Github of een bericht aan de productowner (in de CC :-).

Voor je "link naar het schema" is er denk ik al een issue (vorige week door mij ingeschoten): netwerk-digitaal-erfgoed/dataset-register#859"

So if we decide we want the information on the Metadata tab, then we are free to do that without running into problems with the NDE spec.

@Veldhoen Veldhoen assigned Veldhoen and mwigham and unassigned Veldhoen Feb 20, 2024
@mwigham
Copy link
Contributor Author

mwigham commented Mar 1, 2024

Feedback René:

  • Current interface raises the question 'where is the data?!?'. Linking through to the data is very important so this should be prominent.
  • René doesn't understand the difference between Overview and Metadata. Would expect Metadata to contain the actual metadata of the dataset. The content of these two tabs is frequently the same. Could they be merged?
  • NDE terminology is confusing - e.g. that a DataDownload does not make it possible to download data
  • Would prefer less text, wants to get to the data quickly (MW: probably other users will want the text, so perhaps we can organise it so you can easily choose between reading the text and jumping into the data)
  • Link to showcases from a dataset

@mwigham
Copy link
Contributor Author

mwigham commented Mar 5, 2024

First version for review, see preview here

@mwigham
Copy link
Contributor Author

mwigham commented Mar 21, 2024

@gb-beng adding you to this issue in relation to the discussion about potentially merging the Overview and Metadata tabs

@rozelemarijn
Copy link

review gedaan - moet nog wel ook geïmplementeerd worden voor de engelse versie toch @mwigham?

@mwigham
Copy link
Contributor Author

mwigham commented Mar 27, 2024

@rozelemarijn klopt

Taken:

  • Feedback punten verwerken
  • EN-talige versie maken

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants