Add journal citation #58
Conversation
| @@ -141,6 +141,7 @@ | |||
| - repo_url: https://github.com/QUIVIRR/Enhanced-Data-Sessions | |||
| html_url: https://quivirr.github.io/Enhanced-Data-Sessions/ | |||
| preprint_citation: doi:10.31235/osf.io/eu7yw | |||
| journal_citation: doi:10.5278/ojs.quivirr.v1.2020.a0001 | |||
There was a problem hiding this comment.
Am going to merge this but noting that the DataCite infrastructure that contains the DOI metadata for this DOI is currently failing, so our CI likely will fail. I was able to get metadata from the actual website like:
manubot cite https://doi.org/10.5278/ojs.quivirr.v1.2020.a0001
[
{
"id": "r4Vc1T3N",
"type": "article-journal",
"abstract": "The live ‘data session’ is arguably a significant collaborative practice amongst a group of co-present colleagues that has sustained the fermentation of emerging analyses of interactional phenomena in ethnomethodological conversation analysis for several decades. There has not, however, been much in the way of technological innovation since its inception. In this article, I outline how the data session can be enhanced (a) by using simple technologies to support the ‘silent data session’, (b) by developing software tools to present, navigate and collaborate on new types of video data in novel ways using immersive virtual reality technologies, and (c) by supporting distributed version control to nurture the freedom and safety to collaborate synchronously and asynchronously on the revision of a common transcript used in a live data session. Examples of real cases, technical solutions and best practices are given based on experience. The advantages and limitations of these significant enhancements are discussed in methodological terms with an eye to future developments.",
"container-title": "QuiViRR: Qualitative Video Research Reports",
"DOI": "10.5278/ojs.quivirr.v1.2020.a0001",
"ISSN": "2597-2456",
"language": "en",
"page": "a0001-a0001",
"source": "journals.aau.dk",
"title": "New Technology and Tools to Enhance Collaborative Video Analysis in Live ‘Data Sessions’",
"URL": "https://journals.aau.dk/index.php/QUIVIRR/article/view/a0001",
"volume": "1",
"author": [
{
"family": "McIlvenny",
"given": "Paul"
}
],
"accessed": {
"date-parts": [
[
"2022",
1,
18
]
]
},
"issued": {
"date-parts": [
[
"2020",
12,
1
]
]
},
"note": "This CSL Item was generated by Manubot v0.5.1 from its persistent identifier (standard_id).\nstandard_id: url:https://doi.org/10.5278/ojs.quivirr.v1.2020.a0001"
}
]I think the best course is for us to merge this and then figure out the best way to workaround these DataCite failures.
There was a problem hiding this comment.
And this happened even with manubot 0.5.2, right? We can discuss this elsewhere, but maybe falling back to Zotero with the DOI URL https://doi.org/10.5278/ojs.quivirr.v1.2020.a0001 could be a last resort attempt to retrieve DOI metadata.
There was a problem hiding this comment.
Yes with 0.5.2.
maybe falling back to Zotero with the DOI URL https://doi.org/10.5278/ojs.quivirr.v1.2020.a0001 could be a last resort attempt to retrieve DOI metadata.
I agree this is a good next step.
There was a problem hiding this comment.
I did not have trouble with this DOI with Manubot in 2021. It is only since the new year (and updating to 0.5.2) that this happened. And GitHub Actions build times are lately 3-5 times as long. No idea why... but the main processing hike is with the Build Manuscript.
There was a problem hiding this comment.
@skandilocks one of the main APIs citation metadata is getting pulled from has been having issues, see crosscite/content-negotiation#104 (comment).
One thing that will speed things up tremendously is to cache reference metadata like:
In order to freeze all references, rather than have Manubot regenerate them during future builds, copy the
references.jsonoutput file tocontentwith a filename matching themanual-references*.jsonpattern. One tip is to embed the datereferences.jsonwas generated into the frozen manual reference filename, likecontent/manual-references-2019-06-21.json.
|
@skandilocks that's pretty interesting that the publisher could use the Manubot HTML output for the published rich HTML verison. |
@agitter, well it seemed a waste not to use all those lovely Manubot outputs! As a (digital) humanities scholar, I'd like to say thanks to you all for developing, sharing and maintaining Manubot. |
No description provided.