Skip to content
Please note that GitHub no longer supports your web browser.

We recommend upgrading to the latest Google Chrome or Firefox.

Learn more
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/dataset repository: What CSL variable? #4367

Open
bwiernik opened this issue Oct 17, 2019 · 2 comments

Comments

@bwiernik
Copy link
Contributor

@bwiernik bwiernik commented Oct 17, 2019

Encountering a wrinkle with preprints and datasets. From most preprint repositories, the name of the server is getting stored by Zotero's translators as container-title. This had seemed like a good idea (ala Journal titles). However, I am now seeing that some preprints and many datasets import with container-title used to indicate the collection or larger body of works the item belongs to (e.g., doi.org/10.3886/ICPSR35531.v3).

Conceptually, I think the preprint/data repository makes good conceptual sense as either archive or publisher rather than container-title (this is, for example, how the OSF repositories export in their metadata [as publisher], and CrossRef's posted content type uses "group-id", which would fit well with publisher; ICPSR stores its name in publisher). Most citation styles print publisher, so it seems like this would work well without many changes to existing styles.

Could we come to a consensus as to where these best belong?
(Cross-posted to https://discourse.citationstyles.org/t/preprint-dataset-repository-what-csl-variable/1570)

@stale

This comment has been minimized.

Copy link

@stale stale bot commented Nov 16, 2019

This issue hasn't seen any activity in the past 30 days. It will be automatically closed if no further activity occurs in the next two weeks.

@stale stale bot added the waiting label Nov 16, 2019
@stale stale bot closed this Dec 1, 2019
@adam3smith adam3smith reopened this Dec 1, 2019
@adam3smith adam3smith pinned this issue Dec 1, 2019
@stale stale bot removed the waiting label Dec 1, 2019
@adam3smith

This comment has been minimized.

Copy link
Member

@adam3smith adam3smith commented Dec 1, 2019

(I think we should just not apply stale bot to regular tickets)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.