-
Notifications
You must be signed in to change notification settings - Fork 8
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
Preprint item type #88
Comments
Huh, surprised we don't have a ticket. Edit: just looking at arXiv and wondering if we should try to get the ID into a number field? It needs to be citeable |
How about "repository" for publisher? |
Type mapped to genre. APA style wants the archive ID. We settled on CSL archive_location for that back when we discussed it @adam3smith when I was writing APA 7. |
Do you remember why? |
Let me look into it |
The ids actually get a little tricky. We currently put arXiv IDs (from arXiv.org or Mendeley import) into Extra as Can we just assume that all preprint archives will use an unambiguous id format, with an identifiable prefix like |
I like the archiveID. Not sure if all servers have that - e.g. OSF preprints technically habe an ID but they never use it, but leaving the field empty is fine of course. |
Would we maybe want to add archive ID to all types alongside archive, location in archive, and the new archive place and archival collection? That would unambiguously separate physical and digital locations. CSL could add an archive_id variable |
I like it, I think, particularly the electronic vs. physical but we should
maybe run by some more people?
…Sent from my phone
On Fri, Nov 12, 2021, 08:08 Brenton M. Wiernik ***@***.***> wrote:
Would we maybe want to add archive ID to all types alongside archive,
location in archive, and the new archive place and archival collection?
That would unambiguously separate physical and digital locations. CSL could
add an archive_id variable
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA7PWXRBXSIAAAKORCVVRLULUGTLANCNFSM5H4NQJZQ>
.
|
Does Re: More practically, do styles know not to use the |
CSL 1.0.2 which we are hoping to release on Dec 1 has I'm not sure about the answer to the arxiv questions, but as a data point, arxiv's own bibtex no longer includes the arxiv ID once an item is published in a journal |
Perhaps converting archiveID to an attached link would be a good way to keep the information but also avoid including the ID in citations to published items? |
That's a good idea. |
But then do we still need |
A lot of items might have an electronic archive that should be cited instead of/in addition to a URL. APA for example, wants archive and archive IDs to be included when the item is not widely available (e.g., articles, reports, manuscripts, books, documents). Examples given in the manual are ProQuest ID numbers and ERIC ID numbers.
|
OK, so use the same The only problem would be if you manually changed the item type from Preprint to Journal Article. If it's the same field, the |
This is what I have so far: {
"itemType": "preprint",
"fields": [
{
"field": "title"
},
{
"field": "abstractNote"
},
{
"field": "date"
},
{
"field": "repository",
"baseField": "publisher"
},
{
"field": "place"
},
{
"field": "archiveID"
},
{
"field": "DOI"
},
{
"field": "citationKey"
},
{
"field": "url"
},
{
"field": "accessDate"
},
{
"field": "archive"
},
{
"field": "archiveLocation"
},
{
"field": "shortTitle"
},
{
"field": "language"
},
{
"field": "libraryCatalog"
},
{
"field": "callNumber"
},
{
"field": "rights"
},
{
"field": "extra"
}
],
"creatorTypes": [
{
"creatorType": "author",
"primary": true
},
{
"creatorType": "contributor"
},
{
"creatorType": "editor"
},
{
"creatorType": "translator"
},
{
"creatorType": "reviewedAuthor"
}
]
} Some more questions:
|
@adam3smith Would @denismaier @bdarcus What do you think of adding an |
Agree with Brenton on the above. I think we'll do fine with Edit: which does mean we'll want series and series number added to the above |
And map Document to CSL 1.0.2 `document`
And map Document to CSL 1.0.2 `document`
Anyone have an idea for an icon for preprints? We'll need both a custom one in the new style for iOS/web and something based on famfamfam or Fugue for the desktop client: http://www.famfamfam.com/lab/icons/silk/previews/index_abc.png (Could be a combination of icons if necessary.) |
"script" is sort of funny for this, in a Martin-Luther-nailing-theses-to-the-door sort of way. We're using that for Bill in the client, but our custom icon for Bill is the § symbol, so we could repurpose the script concept for this. For now, I'm going with "receipt", which doesn't make a ton of sense but looks vaguely unfinished — like a piece of paper ripped off a dot matrix printer. |
What about famfamfam's |
"receipt" is the top row above. "bill" is the second. I was just saying we could use the bill concept, but we'd definitely do it in white/gray to be closer to the journal article icon. |
Oh, right. |
Maybe it's just been too many years of seeing the scroll/script used for Bill, but it looks a little weird to me for preprint For famfamfam, I think both From Fugue, I really like |
How about page_white_wrench, because they're (often) still being worked on? |
You could also pick your four favorites options and make it a Twitter poll, create some preprint buzz |
Yes, we'll be changing it. Priority was just getting this out. |
Cool, just wanted to give some feedback in case that wasn't the plan |
Journal article plus pencil, similar to manuscript (blank page plus pencil) Follow-up to zotero/zotero-bits#88
Starting to work on preprint citations -- I'm not getting |
Can you provide a sample minimal style to test that? |
MWE: ArchiveID also doesn't show up in CSL JSON from preprints, but I think that's expected? |
The Zotero field is `archiveID`, not `archive_id`, but this also isn't necessary after making `archiveID` a base-mapped field in 4277955. See zotero/zotero-bits#88 and zotero/zotero#2481
Sorry about that — didn't update a submodule. Try in the latest beta. |
Yup, working, thank you! |
@adam3smith, @bwiernik, is there anything I should be consulting for this? Anything this needs to be mapped to on the CSL side? I'm not seeing any existing issues for it.
The text was updated successfully, but these errors were encountered: