1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
|
see also:
- <http://docs.citationstyles.org/en/stable/specification.html#appendix-iii-types>
- <https://citeproc-js.readthedocs.io/en/latest/csl-m/index.html#unpublished-extension>
"publication status" instead of pre-print and manuscript types
all CSL types (note: can also be null):
- article
- article-magazine
- article-newspaper
- article-journal
- bill
- book
- broadcast
- chapter
- dataset
- entry
- entry-dictionary
- entry-encyclopedia
- figure
- graphic
- interview
- legislation
- legal_case
- manuscript
- map
- motion_picture
- musical_score
- pamphlet
- paper-conference
- patent
- post
- post-weblog
- personal_communication
- report
- review
- review-book
- song
- speech
- thesis
- treaty
- webpage
basics:
- article-journal
- article-magazine
- article-newspaper
- book
- chapter
- dataset
- manuscript
- paper-conference
- post-weblog
- report
- review
- speech
- thesis (aka, dissertation)
- webpage
additional fatcat types:
- software (https://github.com/citation-style-language/zotero-bits/issues/69)
- peer_review
- standard (as in, RFC or ISO)
"paper-like" (for various stats):
- article-journal
- chapter
- paper-conference
- thesis
crossref work types (https://api.crossref.org/types):
- book => book
- book-chapter => chapter
- book-part => chapter
- book-section => chapter
- component => <blank> (or more specific)
- dataset => dataset
- dissertation => thesis
- edited-book => book
- journal-article => article-journal
- monograph => book
- other => <blank>
- peer-review => peer_review (or blank)
- posted-content => post (or more specific)
- proceedings-article => paper-conference
- reference-book => book
- reference-entry => entry (or more specific)
- report => report
- standard => ???
crossref non-work types (don't need mappings; don't import? as containers?
two-layers of containers?)
- book-series
- book-set
- book-track
- journal (definitely not release)
- journal-issue
- journal-volume
- proceedings (definitely not release)
- proceedings-series
- report-series
- standard-series
release statuses should align with DRIVER guidelines, which are:
- draft: Early version circulated as work in progress
- submittedVersion: The version that has been submitted to a journal for peer review
- acceptedVersion: The author-created version that incorporates referee comments and is the accepted for publication version
- publishedVersion: The publisher created published version
- updatedVersion: A version updated since publication
http://web.archive.org/web/20091109125137/http://www2.lse.ac.uk/library/versions/VERSIONS_Toolkit_v1_final.pdf
Proposed fatcat vocabulary:
- draft
- submitted: aka, pre-print, "under review"
- accepted: aka, post-print, author's manuscript, "publisher's proof", "post-print"
- published: the version that the publisher distributes. may include minor
(gramatical, typographical, broken link, aesthetic) corrections. AKA,
"version of record", "final publication version".
- updated: post-publication significant updates (considered a separate release
in fatcat). AKA, "correction" (in the context of "correction notice", or the
full new version)
The term "working paper" can be ambiguous; in some contexts it is a draft, in
some submitted (pre-print).
TODO: retractions (of published works, by author or publisher/editor) and
withdrawls (of un-published but released/submitted works). are these a separate
release, separate flag ("is_retracted"), or status type? if status, is it
"-retracted", eg, "published-retracted", or just "retracted"? should fatcat
point to the specific retraction release/object? that would include, eg, the
date, and other metadata.
I think a "withdrawn_date" schema field, in combination with "retraction"
release type and status, is probably best. If pre-publication, only set
withdrawn date. If post-publication, set the withdrawn_date and also create a
retraction release under the same work (with appropriate status and/or type).
But maybe "is_withdrawn" in case date isn't known?
Links:
- https://arxiv.org/help/withdraw
- https://peerj.com/about/preprints/policies-and-procedures/#retraction-policy
- https://www.elsevier.com/about/policies/article-withdrawal
- https://support.crossref.org/hc/en-us/articles/115000501246-Crossmark-registering-updates
|
