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

Recent ships #674

Open
arfon opened this issue Feb 7, 2020 · 6 comments
Open

Recent ships #674

arfon opened this issue Feb 7, 2020 · 6 comments

Comments

@arfon
Copy link
Member

@arfon arfon commented Feb 7, 2020

I thought it might be good for @openjournals/dev start documenting updates/improvements that have been made recently to JOSS/Whedon etc. in a semi-regular fashion so here's a summary of what's happened recently:

Better support for BibTeX in JOSS & JOSE UI: There's now a couple of links on the JOSS and JOSE paper view which allows for copying of the citation string (the thing shown in the UI) or a BibTeX entry.

Screen_Shot_2020-02-07_at_10_24_30_AM

Sortable table on editor dashboard: It's now possible to sort the list of editors by the number of assignments they have on the dashboard.

Screen_Shot_2020-02-07_at_10_24_08_AM

EiC information now shown on pre-review issue: The pre-review issue now shows which EiC opened up this issue on GitHub #669

Whedon support for withdrawing and rejecting papers: Papers can now be rejected and withdrawn by Whedon #662 #671 openjournals/whedon-api#81 openjournals/whedon-api#79

Better errors in Whedon paper preview service: Whedon now reports errors properly in the preview service openjournals/whedon-api#80

Email invites for authors: It's now possible to invite editors to edit a paper, with an automated email sent to them #673 openjournals/whedon-api#82

Repository statistics now reported in pre-review issue: In order to help editors make decisions about whether submissions are in scope, Whedon now reports some summary statistics in the pre-review thread about the repository openjournals/whedon-api#77

/ cc @openjournals/jose-editors @openjournals/joss-editors

@labarba

This comment has been minimized.

@danielskatz

This comment has been minimized.

Copy link
Collaborator

@danielskatz danielskatz commented Feb 7, 2020

Re the first upgrade, which is great, a future next step would be to have a pulldown where the citation could be exported in a variety of formats - I think @mfenner knows how to do this...

@arfon

This comment has been minimized.

Copy link
Member Author

@arfon arfon commented Feb 7, 2020

I think @mfenner knows how to do this...

Ooo yeah. That would be great. @mfenner any suggestions how to best accomplish this? The views are built with Ruby/Rails so some kind of gem would be great. Otherwise a JavaScript thing could work too.

@mfenner

This comment has been minimized.

Copy link

@mfenner mfenner commented Feb 8, 2020

The easiest way to do this is to use DOI content negotiation to get back the formatted citation, works in any language :). What we have done in DataCite Search and Crossref Metadata Search (originally same source code at https://github.com/crosscite/doi-metadata-search) is hardwire some common styles in a Javascript popup window. You could of course do something similar in a Ruby view.

Crossref and DataCite currently run a separate backend service for citation formatting, but the DataCite service (source code at https://github.com/crosscite/content-negotiation) supports Crossref DOIs, and is arguably better maintained.

DataCite content negotiation supports providing the content type via header or via path:

curl -LH "Accept: "text/x-bibliography; style=ieee" https://data.crosscite.org/10.21105/joss.02004

or

https://data.crosscite.org/text/x-bibliography/10.21105/joss.02004?style=ieee

Our content negotiation of course also supports bibtex:

https://data.crosscite.org/application/x-bibtex/10.21105/joss.02004

@mfenner

This comment has been minimized.

Copy link

@mfenner mfenner commented Feb 8, 2020

For a tighter integration you could also use the bolognese gem (which powers our content-negotiation and citation formatting), but that is probably overkill. https://github.com/datacite/bolognese

@labarba

This comment has been minimized.

Copy link
Member

@labarba labarba commented Feb 8, 2020

a future next step would be to...

The next step is to write out a roadmap, and place feature ideas and requests in some form of priority list. Otherwise important dev work that is harder to complete gets eternally delayed, trumped by shiny nice-to-haves that are easy to do.

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.