iiasa / coacch Goto Github PK

The COACCH-specific metadata has, beyond the Keywords element, further elements that could be used to build the index. Potentially:

• Partner
• Model type/method
• Model
• Sector

Try to enrich the index with these.

The DOI badges shown on the data set pages currently retrieve their graphic via a Zenodo URL. It is better to have all content local (more robust site, fewer connections required to load it). Moreover, the PDF generation does not find the badges.

Retrieve the required badges and include them in the repo as static content.

I have given classifying the datasets a first-order stab. But it can probably be done better given the requisite background knowledge which you @EstherBoere so happen to be in possession of. Hence you have become the lucky assignee of this ticket which involves classifying the datasets better by editing this Python file.

This will be an ongoing task until all datasets have trickled in. It involves binning (putting the right numbers in the right class lists) and, if you care about the order in which the datasets appear in the website, re-ordering the ID numbers in those lists. The syntax is Python dictionary and list syntax, but from just looking at the file, I think it is pretty much self-explanatory. Yes, the last items can have a trailing comma unlike in most other languages.

Once you have modified the file, the website won't update automatically as I will need to run a manual generation step: the file is input to the script that generates the restructured text, at least for now, might turn it into a GitHub Action in the future.

The query and generate notebook currently produces per-dataset ReST output in docs/datasets and may (see issue #8) also accumulate per-dataset badges under docs/_static. The content of these directories should be pruned on/post generation to remove entries that are no longer generated.

The metadata of dataset 5541894 has no CSV header as can be seen by examining the content of the metadata URL. The CSV appears transposed.

@EstherBoere, can you do outreach and ask for a fixed upload?

Either remove (preferred) or change the copyright notification.
Not sure if it needs a Copyright as all the individual files already have a license and it should be distributed under an open license.

If we do need one, then change to "Copyright 2021, IIASA"

Hi Albert,
@acjbrouwer

I wanted to edit the main page to support a bit, but did not succeed to push. Do I need some access rights or is it coming from my git client?

Thanks,
Hugo

git.exe push --progress "origin" master:master
remote: Permission to iiasa/COACCH.git denied to hvalin.
fatal: unable to access 'https://github.com/iiasa/COACCH.git/': The requested URL returned error: 403

git did not exit cleanly (exit code 128) (2922 ms @ 01-Oct-21 15:40:04)

Dear Albert,

Would it be possible to put the acknowledgement and disclaimer instead of sub-pages directly on the main page? Note also there's a small spelling mistake in acknowledgement (it's spelled without the second e).

Could we expand the meta data elements in the sub pages (so not in the main page) with the following elements that should be directly harvestable from the meta data:

• Sector
• Partner
• Keywords
• SSP
• RCP
• Spatial resolution Europe

I am pretty sure now that all datasets can be classified either in the headers of impact assessment, tipping points or policy. @acjbrouwer , could you therefore remove the empty header 'other'?

Dear Albert,

As the changes to be done will likely not be so big anymore, could you remove the 'under construction' logo?
I thought that instead we could add a sentence like: 'Additional datasets will be released upon their finalization within the project'

As requested in issue #7, commit 16664f5 inserted notice on the adding of additional datasets. When all datasets have been added, the notice can be removed. @EstherBoere, as you track the status of the submissions, can you please let me know when they are all released by assigning this issue back to me (upon which I will commence with the removal)?