Create web page / section with list of publications using SasView. (Trac #483)

[ajj]

This will require some trolling of the literature...

Migrated from http://trac.sasview.org/ticket/483

{
    "status": "assigned",
    "changetime": "2019-03-23T14:13:50",
    "_ts": "2019-03-23 14:13:50.376216+00:00",
    "description": "This will require some trolling of the literature...",
    "reporter": "ajj",
    "cc": "",
    "resolution": "",
    "workpackage": "Support Infrastructure",
    "time": "2015-11-24T13:48:02",
    "component": "SasView",
    "summary": "Create web page / section with list of publications using SasView.",
    "priority": "critical",
    "keywords": "",
    "milestone": "Admin Tasks",
    "owner": "krzywon",
    "type": "task"
}

[butlerpd]

Trac update at 2015/12/19 18:44:58: butler changed workpackage from "SasView Bug Fixing" to "SasView Admin"

[smk78]

Trac update at 2015/12/23 15:40:36: smk78 commented:

See http://www.sasview.org/impact.html (note: this is not yet linked from the other web pages).

This list of publications was generated by searching the publications databases of the ACS and the RSC with the search terms "sasview" OR "sansview" OR "DMR-0520547" (the DANSE grant number). Results were collated, re-formatted, input into Excel, sorted, and the duplicates stripped out. The resulting worksheet was then sorted on the journal, output as text, re-formatted for html presentation, and pasted into this web page.

In the process there some very clearly 'suspicious' records (way too early for even DANSE, crazy journal, etc) were identified. These have been removed. ''However'', it is highly likely that the records remaining still contain some bogus entries. The only way to be certain is to go through them one-by-one! :-)

NOTE: The ACS/RSC search engines are very good in that they search all the text in ''both'' the manuscript AND the supplementary information. Capability that far exceeds what Web of Science can do!

[smk78]

Trac update at 2015/12/23 17:23:04: smk78 commented:

On Mathieu's advice have removed all records earlier than 2007 (bit of a no-brainer, really)

Mat adds that we should look carefully at those records that remain that have publication years of 2007, 2008 & 2009.

[ajj]

Trac update at 2017/04/04 21:58:25:

• ajj changed owner from "" to "smk78"
• ajj changed status from "new" to "assigned"

[butlerpd]

Trac update at 2019/02/27 17:48:34:

• butler commented:

Jeff Krzywon had an infrastructure to help with this for NIST SANS instruments. He started a githup repo (pub-tracker) to duplicate that but has since moved the NIST infrastructure to a different approach worked out by Brian Maranville. This should be done soon so we have a sustainable way of finding, entering, and storing the information.

• butler changed owner from "smk78" to "krzywon"
• butler changed workpackage from "SasView Admin" to "Support Infrastructure"

[butlerpd]

Trac update at 2019/03/23 14:13:50: butler changed priority from "major" to "critical"

[krzywon]

The site is up and running, but needs a few finishing touches to be 100% complete.

How it all works:

1. The website displaying the publications is live, but not linked to from sasview.org yet - http://www.sasview.org/publications/ which is generated using the publications.md file at https://github.com/SasView/sasview.github.io
2. The site is updated when the list of publications at https://www.zotero.org/groups/2309096/sasview is modified. Currently @ajj and I are the only two with write access to the zotero group.
3. The site is generated using source from https://github.com/krzywon/saspubs. instrument_zotero_feed.py generates a json file with all of the bibliographic information and then runs citeproc_to_html.py which converts the json to markdown using the format outlined in ./static/Sasview_linktitle.csl.
4. On the DANSE server, a job runs push_updates.sh every hour. The bash script assumes a single argument be the location of an SSH key file that is linked to a github account with write access to sasview.github.io. The bash script pulls the latest updates from saspubs and sasview.github.io, runs instrument_zotero_feed.py, commits any changes made to publications.md ("publications auto-update "), and then pushes.

Things left to do:

1. Create a github account dedicated to preforming automated tasks like this. This account should only have write access to the specific files it needs to update (sasview.github.io/publications.md is the only one currently). This account could be used for other automated tasks link online docs and creating news items after a release build, among others.
2. Create a DANSE server account dedicated to automated sasview tasks, and have this account run the job. The job should run more often than every hour.
3. Give more people access to the saspubs repo, or fork it into sasview.
4. Give more people write access to the zotero group. @butlerpd, @wpotrzebowski, @smk78 were my initial thoughts.
5. Sanitize the publications list. Many need verifying and some are lacking a DOI.
6. Once all of this is done, add a link the pubs site from the About menu on sasview.org.