-
Notifications
You must be signed in to change notification settings - Fork 208
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
Create full formatting spec #16
Comments
@yangkky would you want to try to automate some of the citation metadata extraction and formatting? I started thinking about how our Manubot tool might be able to take a list of conference paper URLs, arXiv ids, journal DOIs, etc. and generate the formatted reference list for collaborative curation projects like this (manubot/rootstock#223). The goal would be to make it easier to maintain and contribute to. |
Yes, that would be awesome! |
There are a few options for setting this up. All of them would involve listing references in this repository, using Manubot (with pandoc and CSL) to extract and format the metadata, and deploying the formatted list. Option 1: Full manuscript Option 2: Keep the references in the readme Option 3: Custom GitHub pages |
In principle, I like option 1 a lot, especially as I'd eventually like to add some paper summaries. Under this option, the final product would have it's own webpage, backed by the github repo, right? |
Yes, with option 1 there is a GitHub repository that contains Markdown files with references and discussions of some or all references. Those are built into HTML and PDF documents on the You can edit the demo at https://github.com/manubot/try-manubot/ to see how option 1 works. The files in the |
Great! I'll give this a try when I have some time! |
I've found this repo to be very useful, so I'm returning to this issue to see if there is a way to reduce the maintenance burden. I prototyped a GitHub Actions workflow that will automatically extract the citation information from the title of a new issue. The idea is that you and other contributors could quickly make new issues with relevant papers and periodically make a batch update to the readme categorizing those new papers. The manual step of copying and formatting the reference would be eliminated. You can see what this looks like in agitter/manubot-awesome-list#7 or test it by opening a new issue in that repo. Title field can be a URL to a paper, a DOI, arXiv id, PMID, or any other identifier that Manubot supports. The action only runs on issues with the I also made a Citation Style Language file that modifies the Manubot default to approximately match the reference style in this repo. Let me know if this seems useful. I could make a pull request to enable the issue processing here. |
Hi Anthony,
Sorry for the slow response. This sounds great! If you make a pr I'll
definitely review it.
…On Thu, Oct 29, 2020, 5:19 PM Anthony Gitter ***@***.***> wrote:
I've found this repo to be very useful, so I'm returning to this issue to
see if there is a way to reduce the maintenance burden. I prototyped a
GitHub Actions workflow that will automatically extract the citation
information from the title of a new issue. The idea is that you and other
contributors could quickly make new issues with relevant papers and
periodically make a batch update to the readme categorizing those new
papers. The manual step of copying and formatting the reference would be
eliminated.
You can see what this looks like in agitter/manubot-awesome-list#7
<agitter/manubot-awesome-list#7> or test it by
opening a new issue in that repo. Title field can be a URL to a paper, a
DOI, arXiv id, PMID, or any other identifier that Manubot supports
<https://github.com/manubot/rootstock/blob/master/USAGE.md#citations>.
The action only runs on issues with the reference label.
I also made a Citation Style Language file
<https://github.com/agitter/manubot-awesome-list/blob/master/style.csl>
that modifies the Manubot default to approximately match the reference
style in this repo.
Let me know if this seems useful. I could make a pull request to enable
the issue processing here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADEMNWDCJ5YRIIZSCNG2X3TSNHL5BANCNFSM4HZVGHAA>
.
|
No description provided.
The text was updated successfully, but these errors were encountered: