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
|
bibtex
BIBFRAME
schema.org: http://schema.org/CreativeWork
dublin core
entity specific:
- crossref / release
- orcid / creator
- issn / container
## Dublin Core (original/simple)
Usage guide: <http://www.dublincore.org/documents/usageguide/elements/>
Quick descriptions of the "original 15" fields: <http://mn.gov/bridges/dcore.html>
## Citation Style Language
Human-readable specification: <http://docs.citationstyles.org/en/1.0.1/specification.html>
Specifically, the "variables" and type definitions: <http://docs.citationstyles.org/en/stable/specification.html#appendix-iv-variables>
"extra" fields:
- medium (CD, DVD; from CSL)
- genre (Phd vs. masters thesis? from CSL)
- rights/license (for explicit OA)
- version (eg, for software, standards)
- url (eg, for blog posts and other web content; canonical only)
- authority (for things like patents)
- collection_title (for book series)
- short_title
- edition (eg, "4th")
- event (eg, conference)
- chapter_number
- submitted
"extra" for citations:
- most of the above, or any fields from 'release"
- authors (an array)
- url
- issue, volume, date, edition
- accessed_date
release_date aligns with... 'issued'? not original-date
pages aligns with 'page'. Should this be 'locator'?
other things:
- anything specially needed for a blog post? url (original/canonical)?
- press_release
more serious schema issues:
- add arxiv id (for easier aggressive import)
- two levels of container? something for both "series" and "specific year of
conference". nested seems to get out of hand. for now, just a
"series-container" string in extra?
- for chapter/book relations, a `part_of` field for release_rev to release_ident
- ok, now I understand the whole "date-parts" business. hrm, maybe need to have
3 columns or use a string format
|
