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

Update Instruction to make User dataset public in RDM UI #13

Open
jdries opened this issue May 2, 2024 · 16 comments
Open

Update Instruction to make User dataset public in RDM UI #13

jdries opened this issue May 2, 2024 · 16 comments
Assignees

Comments

@jdries
Copy link

jdries commented May 2, 2024

No description provided.

@santoshkaranam santoshkaranam changed the title allow making user dataset public Update Instruction to make User dataset public in RDM UI May 2, 2024
@jdegerickx
Copy link

we would need a web form for the user to complete the necessary additional information required...
Hendrik is working on a list of items to inquire...

@kvantricht
Copy link

Meeting to be organized between IIASA and WENR.

@boog-wur
Copy link

Before organize a meeting I would like to prepare some documents:

  • Define protocol how to publish
  • Prepare overview how metadata must be organized and completed
  • Prepare a Word template with placeholders to support automated generation

@boog-wur
Copy link

boog-wur commented Jul 16, 2024

@boog-wur
Copy link

One other question for @santoshkaranam : In the RDM UI I see the Title (top part) and the DataSet Name (bottom part). These are different? And where does this come from? The DataSet Name by the data holder during upload? Is then the Title created by the moderator?

@santoshkaranam
Copy link
Collaborator

@boog-wur in the metadata files, these are autogenerated, hence gray cell in Excel sheet. The title at both places is the same.
The title is given at the time of upload. The tile can also be edited later, collectionID cannot be edited

image

@boog-wur
Copy link

@santosh: you refer to the new phase 2 data sets? For the phase 1 data sets there is a difference between Title and DataSet Name, right? Anyway, that is no problem, we can keep these differences for the phase 1 data set. Do you agree?

@santoshkaranam
Copy link
Collaborator

So i checked the Metadata from Phase1 - Phase1 website - https://worldcereal-rdm.geo-wiki.org/collections/
image

The name refers to collectionID and both are the same, so are in phase2 also , yes we can keep them as is.

@boog-wur
Copy link

@santoshkaranam : we have a misunderstanding. I refer to other fields. See attached screen dump. There you so title that differs from a the data set name.
image

@santoshkaranam
Copy link
Collaborator

@boog-wur, so the top title is for the harmonized dataset inside the RDM. The bottom "dataset Name" field is the original dataset name, if available. And yes, we can keep both for phase 2 as well. If user knows the original dataset name, user can provide

@boog-wur
Copy link

In Phase 1 we had a name for the original data (OriginalDataSet:NameDataSet::). This is the name the data holder / user will give during upload and is presented in the UI bottom (Dataset Name). In Phase 1 we had several entries for the curated data set:

  • CuratedDataSet:ReferenceCuratedDataSet:NameCuratedDataSet: (actually the filename)
  • CuratedDataSet::TitleCuratedDataSet: (UI: Top - title)
  • CuratedDataSet::DescriptionCuratedDataSet: (UI: Top - description)

In Phase 2 we want to keep it simpler. We have:

  • OriginalDataSet:NameDataSet:: provided by the data holder / user during upload. We could keep it in the UI (Bottom - Dataset Name)
  • Keep CuratedDataSet::TitleCuratedDataSet: (UI: Top - title)
  • Skip CuratedDataSet::DescriptionCuratedDataSet: (UI: Top - description)

Then the issue is when we ask for the title? It must be short and easy to recognize. Could it be the same as the name provided by the data holder / user during upload. Thus the same as OriginalDataSet:NameDataSet::? And use it for both the UI Top Title and UI Bottom Dataset Name. Then during publishing we can adapt the Title in case it is too long and less attrative for the public.

@jdegerickx
Copy link

I agree trying to keep things simple. Only asking the user to provide a short name (which can then be used to compile the official collectionID) + a short description during dataset upload and then use that one as much as possible.

@jdegerickx
Copy link

@boog-wur, I have reviewed your excel file and provided some comments in columns H/I. Thanks for preparing!

@boog-wur
Copy link

@jdegerickx : thanks, I updated some cells and replied to your comments

@boog-wur
Copy link

Now that the metadata is more or less clear I worked on the protocol on how to publish harmonized data. I wrote a text that can be shown in case the user decides to publish the data (button "share with consortium", perhaps better to call it "share with community").

Before we can publish this text the metadata editor should be ready. See previous discussion. For now we could just show one line that user have to contact the WorldCereal moderator if they want to share.

See this link for the text on the publication pages:
https://vitoresearch.sharepoint.com/:w:/r/sites/21717-ccn-world-cereal/Shared%20Documents/System/RDM/Instructions%20to%20publish%20data.docx?d=wb6dde3b6c44143aca5a1200909176c0b&csf=1&web=1&e=5v8ZTR

Finally I need to create a template with placeholders for the harmonization document

@boog-wur
Copy link

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

5 participants