Add links to curation pages

[carlinmack]

2nd half of closing #1322
Close #1122

This PR adds a link to the curation page for all Q number pages.

This PR relies on #1552 as the curation aspect chooser is filtered based upon whether there is a useful curation page for that aspect. On this curation page, the aspect chooser is filtered of the aspects which don't have curation page templates:

---

I'm happy with this PR now, text below preserved for reference

---

This needs some iteration/discussion before it's ready, due to design choices etc.

The position was chosen as users are accustomed to finding edit controls in the top right of the page.

In terms of the text:

• "Edit" would have to direct the user to Wikidata, which would be odd
• "Curate" does make sense if you have the right mental model, but would be initially confusing to the user (especially with the current page, more on this below).
• "Add more info" is clearer, but not ideal
• I've gone with "Improve data" as this doesn't have the connotation of directly editing

I have no comment on what the URL of the curation pages should be, I do prefer "curation" to "missing"

In terms of the curation page itself, I think it needs some work, definitely in regards to #374. As far as I can tell, this page largely functions to provide quick access to (hopefully) fruitful Author Disambiguator pages and Wikidata pages that have missing properties. As a user I would expect this page to provide some context of where information comes from, where it can be added, what tools are available, and then links to pages on these tools.

If we take the user story "As an academic, I want to add a notable paper to an academic's page, so that the Scholia profile is more complete", there is no direction for the best way to do something like this, and what tools are available to do this.

There is currently a hardcoded list of valid aspects for curation, but if we can close #281 then we do not need this.

I will work on a prototype of this in another PR :)

PR has been created

[carlinmack]

Oops, still need to handle this bit of code:

// this query opens a subpage for the Wikidata item, e.g. as cito subpage
     var endpointUrl = 'https://query.wikidata.org/sparql';
     var query = `
    SELECT DISTINCT ?aspectsubpage
    WHERE {
    { [] pq:P3712 / wdt:P31 wd:Q96471816 ; ps:P2860 / wdt:P1433 wd:{{ q }} . BIND("venue-cito" AS ?aspectsubpage) }
    UNION
    { [] pq:P3712 / wdt:P31 wd:Q96471816 ; ps:P2860 wd:{{ q }} . BIND("work-cito" AS ?aspectsubpage) }
    }
    `;
     settings = {
	 headers: { Accept: 'application/sparql-results+json' },
	 data: { query: query }
     };

     $.ajax( endpointUrl, settings ).then( function ( data ) {
	 data.results.bindings.forEach(function(entry) {
	     var props = entry.aspectsubpage.value.split("-");
	     var aspect = props[0];
	     var subpage = props[1];
	     $( '#aspect-chooser' ).append(
		 `<a role="button"
		     class="btn btn-outline-dark btn-sm"
                     href="{{ url_for('app.index') }}` + aspect + '/' + '{{ q }}' + '/' + subpage + '">' + subpage + '</a> ' );
	 });
     } );

[carlinmack]

As of #1610 , I will not handle that bit of code in this PR, and instead close #741 first

[fnielsen]

I am trying to understand what should be done with this PR. Should I review and merge it? And the work can continue from there? Currently there is no automatic testing.

[carlinmack]

Actually I think it is fine now, can't quite recall why this wasn't marked as ready for review

[Daniel-Mietchen]

This also fixes #1708

[Daniel-Mietchen]

Looks good and works fine.

[Daniel-Mietchen]

Adding a pointer to

• Scholia hackathon on 14 and 16 February 2022 #1807

which serves to keep an overview of things we worked on during the hackathon.