commonmeta-ruby 3.2.3 → 3.2.4

Sign up to get free protection for your applications and to get access to all the features.
Files changed (35) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +1 -1
  3. data/lib/commonmeta/author_utils.rb +11 -0
  4. data/lib/commonmeta/cli.rb +5 -1
  5. data/lib/commonmeta/readers/json_feed_reader.rb +9 -5
  6. data/lib/commonmeta/utils.rb +4 -2
  7. data/lib/commonmeta/version.rb +1 -1
  8. data/spec/author_utils_spec.rb +9 -8
  9. data/spec/cli_spec.rb +1 -1
  10. data/spec/fixtures/vcr_cassettes/Commonmeta_CLI/json_feed/blog_post.yml +14 -14
  11. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed/all_posts.yml +2625 -0
  12. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed/behind_the_science.yml +1176 -0
  13. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/blogger_post.yml +7 -7
  14. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_with_doi.yml +7 -7
  15. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_without_doi.yml +196 -0
  16. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/jekyll_post.yml +7 -7
  17. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/wordpress_post.yml +7 -7
  18. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/json_feed_url/all_posts.yml +221 -0
  19. data/spec/readers/json_feed_reader_spec.rb +35 -10
  20. data/spec/utils_spec.rb +5 -0
  21. data/spec/writers/citation_writer_spec.rb +1 -1
  22. metadata +6 -15
  23. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_metadata/blogger_post.yml +0 -141
  24. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_metadata/ghost_post_with_doi.yml +0 -164
  25. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_metadata/jekyll_post.yml +0 -134
  26. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_metadata/wordpress_post.yml +0 -210
  27. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_item_metadata/blogger_post.yml +0 -94
  28. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_item_metadata/ghost_post.yml +0 -117
  29. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_item_metadata/ghost_post_with_doi.yml +0 -117
  30. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_item_metadata/jekyll_post.yml +0 -170
  31. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_item_metadata/wordpress_post.yml +0 -163
  32. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_post_metadata/blogger_post.yml +0 -141
  33. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_post_metadata/ghost_post_with_doi.yml +0 -164
  34. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_post_metadata/jekyll_post.yml +0 -134
  35. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_post_metadata/wordpress_post.yml +0 -210
@@ -1,117 +0,0 @@
1
- ---
2
- http_interactions:
3
- - request:
4
- method: get
5
- uri: https://rogue-scholar.org/api/posts/1jgo8yel
6
- body:
7
- encoding: UTF-8
8
- string: ''
9
- headers:
10
- Connection:
11
- - close
12
- Host:
13
- - rogue-scholar.org
14
- User-Agent:
15
- - http.rb/5.1.1
16
- response:
17
- status:
18
- code: 200
19
- message: OK
20
- headers:
21
- Age:
22
- - '0'
23
- Cache-Control:
24
- - public, max-age=0, must-revalidate
25
- Content-Length:
26
- - '6894'
27
- Content-Type:
28
- - application/json; charset=utf-8
29
- Date:
30
- - Sun, 04 Jun 2023 07:20:26 GMT
31
- Etag:
32
- - '"r1h98s95tn5bh"'
33
- Server:
34
- - Vercel
35
- Strict-Transport-Security:
36
- - max-age=63072000
37
- X-Matched-Path:
38
- - "/api/posts/[slug]"
39
- X-Vercel-Cache:
40
- - MISS
41
- X-Vercel-Id:
42
- - fra1::iad1::pkzgk-1685863226488-42890f58a873
43
- Connection:
44
- - close
45
- body:
46
- encoding: UTF-8
47
- string: '{"id":"https://doi.org/10.53731/4nwxn-frt36","short_id":"1jgo8yel","url":"https://blog.front-matter.io/posts/does-it-compose/","title":"Does
48
- it compose?","summary":"One question I have increasingly asked myself in the
49
- past few years. Meaning Can I run this open source software using Docker containers
50
- and a Docker Compose file?As the Docker project turned ten this...","date_published":"2023-05-16T11:36:56Z","date_modified":"2023-05-16T11:36:56Z","authors":[{"url":"https://orcid.org/0000-0003-1419-2405","name":"Martin
51
- Fenner"}],"image":"https://images.unsplash.com/photo-1523351964962-1ee5847816c3?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3wxMTc3M3wwfDF8c2VhcmNofDUzfHxjb250YWluZXJ8ZW58MHx8fHwxNjg0MjMyMTQ0fDA&ixlib=rb-4.0.3&q=80&w=2000","content_html":"
52
- <p><img src=\"https://images.unsplash.com/photo-1523351964962-1ee5847816c3?crop&#x3D;entropy&cs&#x3D;tinysrgb&fit&#x3D;max&fm&#x3D;jpg&ixid&#x3D;M3wxMTc3M3wwfDF8c2VhcmNofDUzfHxjb250YWluZXJ8ZW58MHx8fHwxNjg0MjMyMTQ0fDA&ixlib&#x3D;rb-4.0.3&q&#x3D;80&w&#x3D;2000\"></p><p>One
53
- question I have increasingly asked myself in the past few years. Meaning </p><blockquote>Can
54
- I run this open source software  using Docker containers and a Docker Compose
55
- file?</blockquote><p>As the Docker project <a href=\"https://snyk.io/blog/the-docker-project-turns-10/\">turned
56
- ten this spring</a>, it has become standard practice to distribute open source
57
- software via Docker images and to provide a <a href=\"https://docs.docker.com/compose/\">Docker
58
- Compose</a> file to run the software together with other dependencies. The
59
- <a href=\"https://github.com/docker/awesome-compose\">Awesome Compose</a>
60
- project has collected many examples, and all you need is a <code>docker-compose.yml</code>file
61
- and a recent installation of Docker, e.g. <a href=\"https://www.docker.com/products/docker-desktop/\">Docker
62
- Desktop</a>. Be aware that Docker Compose has evolved over the years. It started
63
- out as a dedicated Python application but was later integrated into the Docker
64
- application (written in Go) as Compose V2.</p><p>Docker and Docker Compose
65
- allow you to run pretty complex applications without first addressing a long
66
- list of requirements (which might conflict with other software you have installed),
67
- or needing a long and complex build step where many things can go wrong. For
68
- example a self-hosted instance of Supabase (a hosted Postgres database with
69
- additional features) that I installed last week following <a href=\"https://supabase.com/docs/guides/self-hosting/docker\">these
70
- instructions</a>.</p><p>An important open source project that I am involved
71
- in is <a href=\"https://inveniordm.docs.cern.ch/\">InvenioRDM</a>, the turn-key
72
- research data management repository. InvenioRDM started in 2019, with a first
73
- production-suitable version in August 2021, and the <a href=\"https://inveniosoftware.org/products/rdm/#status\">next
74
- major goal </a>is to have the large and popular <a href=\"https://zenodo.org/\">Zenodo</a>
75
- repository running on top of InvenioRDM. Zenodo <a href=\"https://blog.zenodo.org/2023/05/08/2023-05-08-10years/\">turned
76
- ten last week</a>, a few weeks after Docker. Interestingly, my personal tenth
77
- anniversary was last year in May as I became a full-time software developer
78
- and left academic medicine as a medical doctor treating cancer patients in
79
- <a href=\"https://doi.org/10.53731/r294649-6f79289-8cw2j\">May 2012</a>.</p><p>Unfortunately,
80
- InvenioRDM \"doesn''t compose\" yet. It is very close, but there are no ready-made
81
- Docker images to download, and the <a href=\"https://inveniordm.docs.cern.ch/install/\">installation
82
- instructions</a> start with installing a Python command-line tool (invenio-cli).
83
- So if you have 1-2 hours to play with InvenioRDM and get a first impression,
84
- there is no official solution from the InvenioRDM project yet. For this reason,
85
- I started the <a href=\"https://github.com/front-matter/docker-invenio-rdm\">docker-invenio-rdm</a>
86
- repository on Github. It contains a Docker Compose file that uses pre-built
87
- Docker images, and using that file with a <code>docker compose up</code>command
88
- on your local computer should give you a running InvenioRDM within 15 minutes:</p><figure
89
- class=\"kg-card kg-image-card\"><img src=\"https://blog.front-matter.io/content/images/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png\"
90
- class=\"kg-image\" alt loading=\"lazy\" width=\"2000\" height=\"1210\" srcset=\"https://blog.front-matter.io/content/images/size/w600/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
91
- 600w, https://blog.front-matter.io/content/images/size/w1000/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
92
- 1000w, https://blog.front-matter.io/content/images/size/w1600/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
93
- 1600w, https://blog.front-matter.io/content/images/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
94
- 2193w\" sizes=\"(min-width: 720px) 720px\"></figure><p>I started this recently
95
- and obviously want to move forward in two directions:</p><ul><li>fine-tune
96
- the initial configuration to provide a great initial experience with InvenioRDM,
97
- e.g. making it easy to <a href=\"https://inveniordm.docs.cern.ch/develop/topics/theming/\">theme</a>
98
- the InvenioRDM instance</li><li>make this an official part of the InvenioRDM
99
- project, extending the <a href=\"https://github.com/inveniosoftware/docker-invenio\">docker-invenio</a>
100
- GitHub repository that provides Docker base images for InvenioRDM and other
101
- projects using the Invenio software.</li></ul><p>But of course, Docker Compose
102
- is not the answer to all questions regarding running Docker-based infrastructure.
103
- For production environments, most people shy away from using Docker Compose.
104
- The reasons for that and the alternatives will be the topic of a future blog
105
- post (spoiler: there is exciting news).</p><p>Docker Compose also needs more
106
- work to be set up correctly for development environments. It is a common practice
107
- and a workflow I used while working at DataCite (where we launched Docker-based
108
- infrastructure in 2016), but for now, the easiest way to set up InvenioRDM
109
- development environments is using the <a href=\"https://inveniordm.docs.cern.ch/install/\">invenio-cli
110
- tool with a local development environment</a>.</p><p>Please reach out to me
111
- with feedback on running Docker Compose for InvenioRDM (use the <a href=\"https://github.com/front-matter/docker-invenio-rdm/discussions\">discussions</a>
112
- feature in the GitHub repo), or if you have questions about running InvenioRDM
113
- in production.</p> ","tags":["News"],"language":"en","blog_id":"f0m0e38","blog":{"id":"f0m0e38","title":"Front
114
- Matter","language":"en","favicon":"https://blog.front-matter.io/favicon.png","feed_url":"https://blog.front-matter.io/atom/","home_page_url":"https://blog.front-matter.io/","license":"https://creativecommons.org/licenses/by/4.0/legalcode","category":"Engineering
115
- and Technology"}}'
116
- recorded_at: Sun, 04 Jun 2023 07:20:26 GMT
117
- recorded_with: VCR 6.1.0
@@ -1,117 +0,0 @@
1
- ---
2
- http_interactions:
3
- - request:
4
- method: get
5
- uri: https://rogue-scholar.org/api/posts/1jgo8yel
6
- body:
7
- encoding: UTF-8
8
- string: ''
9
- headers:
10
- Connection:
11
- - close
12
- Host:
13
- - rogue-scholar.org
14
- User-Agent:
15
- - http.rb/5.1.1
16
- response:
17
- status:
18
- code: 200
19
- message: OK
20
- headers:
21
- Age:
22
- - '0'
23
- Cache-Control:
24
- - public, max-age=0, must-revalidate
25
- Content-Length:
26
- - '6894'
27
- Content-Type:
28
- - application/json; charset=utf-8
29
- Date:
30
- - Sun, 04 Jun 2023 07:21:03 GMT
31
- Etag:
32
- - '"r1h98s95tn5bh"'
33
- Server:
34
- - Vercel
35
- Strict-Transport-Security:
36
- - max-age=63072000
37
- X-Matched-Path:
38
- - "/api/posts/[slug]"
39
- X-Vercel-Cache:
40
- - MISS
41
- X-Vercel-Id:
42
- - fra1::iad1::c2lh5-1685863263309-757188c1cf71
43
- Connection:
44
- - close
45
- body:
46
- encoding: UTF-8
47
- string: '{"id":"https://doi.org/10.53731/4nwxn-frt36","short_id":"1jgo8yel","url":"https://blog.front-matter.io/posts/does-it-compose/","title":"Does
48
- it compose?","summary":"One question I have increasingly asked myself in the
49
- past few years. Meaning Can I run this open source software using Docker containers
50
- and a Docker Compose file?As the Docker project turned ten this...","date_published":"2023-05-16T11:36:56Z","date_modified":"2023-05-16T11:36:56Z","authors":[{"url":"https://orcid.org/0000-0003-1419-2405","name":"Martin
51
- Fenner"}],"image":"https://images.unsplash.com/photo-1523351964962-1ee5847816c3?crop&#x3D;entropy&cs&#x3D;tinysrgb&fit&#x3D;max&fm&#x3D;jpg&ixid&#x3D;M3wxMTc3M3wwfDF8c2VhcmNofDUzfHxjb250YWluZXJ8ZW58MHx8fHwxNjg0MjMyMTQ0fDA&ixlib&#x3D;rb-4.0.3&q&#x3D;80&w&#x3D;2000","content_html":"
52
- <p><img src=\"https://images.unsplash.com/photo-1523351964962-1ee5847816c3?crop&#x3D;entropy&cs&#x3D;tinysrgb&fit&#x3D;max&fm&#x3D;jpg&ixid&#x3D;M3wxMTc3M3wwfDF8c2VhcmNofDUzfHxjb250YWluZXJ8ZW58MHx8fHwxNjg0MjMyMTQ0fDA&ixlib&#x3D;rb-4.0.3&q&#x3D;80&w&#x3D;2000\"></p><p>One
53
- question I have increasingly asked myself in the past few years. Meaning </p><blockquote>Can
54
- I run this open source software  using Docker containers and a Docker Compose
55
- file?</blockquote><p>As the Docker project <a href=\"https://snyk.io/blog/the-docker-project-turns-10/\">turned
56
- ten this spring</a>, it has become standard practice to distribute open source
57
- software via Docker images and to provide a <a href=\"https://docs.docker.com/compose/\">Docker
58
- Compose</a> file to run the software together with other dependencies. The
59
- <a href=\"https://github.com/docker/awesome-compose\">Awesome Compose</a>
60
- project has collected many examples, and all you need is a <code>docker-compose.yml</code>file
61
- and a recent installation of Docker, e.g. <a href=\"https://www.docker.com/products/docker-desktop/\">Docker
62
- Desktop</a>. Be aware that Docker Compose has evolved over the years. It started
63
- out as a dedicated Python application but was later integrated into the Docker
64
- application (written in Go) as Compose V2.</p><p>Docker and Docker Compose
65
- allow you to run pretty complex applications without first addressing a long
66
- list of requirements (which might conflict with other software you have installed),
67
- or needing a long and complex build step where many things can go wrong. For
68
- example a self-hosted instance of Supabase (a hosted Postgres database with
69
- additional features) that I installed last week following <a href=\"https://supabase.com/docs/guides/self-hosting/docker\">these
70
- instructions</a>.</p><p>An important open source project that I am involved
71
- in is <a href=\"https://inveniordm.docs.cern.ch/\">InvenioRDM</a>, the turn-key
72
- research data management repository. InvenioRDM started in 2019, with a first
73
- production-suitable version in August 2021, and the <a href=\"https://inveniosoftware.org/products/rdm/#status\">next
74
- major goal </a>is to have the large and popular <a href=\"https://zenodo.org/\">Zenodo</a>
75
- repository running on top of InvenioRDM. Zenodo <a href=\"https://blog.zenodo.org/2023/05/08/2023-05-08-10years/\">turned
76
- ten last week</a>, a few weeks after Docker. Interestingly, my personal tenth
77
- anniversary was last year in May as I became a full-time software developer
78
- and left academic medicine as a medical doctor treating cancer patients in
79
- <a href=\"https://doi.org/10.53731/r294649-6f79289-8cw2j\">May 2012</a>.</p><p>Unfortunately,
80
- InvenioRDM \"doesn''t compose\" yet. It is very close, but there are no ready-made
81
- Docker images to download, and the <a href=\"https://inveniordm.docs.cern.ch/install/\">installation
82
- instructions</a> start with installing a Python command-line tool (invenio-cli).
83
- So if you have 1-2 hours to play with InvenioRDM and get a first impression,
84
- there is no official solution from the InvenioRDM project yet. For this reason,
85
- I started the <a href=\"https://github.com/front-matter/docker-invenio-rdm\">docker-invenio-rdm</a>
86
- repository on Github. It contains a Docker Compose file that uses pre-built
87
- Docker images, and using that file with a <code>docker compose up</code>command
88
- on your local computer should give you a running InvenioRDM within 15 minutes:</p><figure
89
- class=\"kg-card kg-image-card\"><img src=\"https://blog.front-matter.io/content/images/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png\"
90
- class=\"kg-image\" alt loading=\"lazy\" width=\"2000\" height=\"1210\" srcset=\"https://blog.front-matter.io/content/images/size/w600/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
91
- 600w, https://blog.front-matter.io/content/images/size/w1000/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
92
- 1000w, https://blog.front-matter.io/content/images/size/w1600/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
93
- 1600w, https://blog.front-matter.io/content/images/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
94
- 2193w\" sizes=\"(min-width: 720px) 720px\"></figure><p>I started this recently
95
- and obviously want to move forward in two directions:</p><ul><li>fine-tune
96
- the initial configuration to provide a great initial experience with InvenioRDM,
97
- e.g. making it easy to <a href=\"https://inveniordm.docs.cern.ch/develop/topics/theming/\">theme</a>
98
- the InvenioRDM instance</li><li>make this an official part of the InvenioRDM
99
- project, extending the <a href=\"https://github.com/inveniosoftware/docker-invenio\">docker-invenio</a>
100
- GitHub repository that provides Docker base images for InvenioRDM and other
101
- projects using the Invenio software.</li></ul><p>But of course, Docker Compose
102
- is not the answer to all questions regarding running Docker-based infrastructure.
103
- For production environments, most people shy away from using Docker Compose.
104
- The reasons for that and the alternatives will be the topic of a future blog
105
- post (spoiler: there is exciting news).</p><p>Docker Compose also needs more
106
- work to be set up correctly for development environments. It is a common practice
107
- and a workflow I used while working at DataCite (where we launched Docker-based
108
- infrastructure in 2016), but for now, the easiest way to set up InvenioRDM
109
- development environments is using the <a href=\"https://inveniordm.docs.cern.ch/install/\">invenio-cli
110
- tool with a local development environment</a>.</p><p>Please reach out to me
111
- with feedback on running Docker Compose for InvenioRDM (use the <a href=\"https://github.com/front-matter/docker-invenio-rdm/discussions\">discussions</a>
112
- feature in the GitHub repo), or if you have questions about running InvenioRDM
113
- in production.</p> ","tags":["News"],"language":"en","blog_id":"f0m0e38","blog":{"id":"f0m0e38","title":"Front
114
- Matter","language":"en","favicon":"https://blog.front-matter.io/favicon.png","feed_url":"https://blog.front-matter.io/atom/","home_page_url":"https://blog.front-matter.io/","license":"https://creativecommons.org/licenses/by/4.0/legalcode","category":"Engineering
115
- and Technology"}}'
116
- recorded_at: Sun, 04 Jun 2023 07:21:03 GMT
117
- recorded_with: VCR 6.1.0
@@ -1,170 +0,0 @@
1
- ---
2
- http_interactions:
3
- - request:
4
- method: get
5
- uri: https://rogue-scholar.org/api/posts/1jdkoe52
6
- body:
7
- encoding: UTF-8
8
- string: ''
9
- headers:
10
- Connection:
11
- - close
12
- Host:
13
- - rogue-scholar.org
14
- User-Agent:
15
- - http.rb/5.1.1
16
- response:
17
- status:
18
- code: 200
19
- message: OK
20
- headers:
21
- Age:
22
- - '0'
23
- Cache-Control:
24
- - public, max-age=0, must-revalidate
25
- Content-Length:
26
- - '3760'
27
- Content-Type:
28
- - application/json; charset=utf-8
29
- Date:
30
- - Sun, 04 Jun 2023 10:18:36 GMT
31
- Etag:
32
- - '"s9i5zuh1o62w6"'
33
- Server:
34
- - Vercel
35
- Strict-Transport-Security:
36
- - max-age=63072000
37
- X-Matched-Path:
38
- - "/api/posts/[slug]"
39
- X-Vercel-Cache:
40
- - MISS
41
- X-Vercel-Id:
42
- - fra1::iad1::p7tvx-1685873912215-b62d20998ec5
43
- Connection:
44
- - close
45
- body:
46
- encoding: UTF-8
47
- string: '{"id":"https://citationstyles.org/2014/01/29/mendeley-donates-to-the-csl-project/","short_id":"1jdkoe52","url":"https://citationstyles.org/2014/01/29/mendeley-donates-to-the-csl-project/","title":"Mendeley
48
- Donates to the CSL Project","summary":"CSL has seen a lot of growth in recent
49
- years: more than 20 software products use CSL (see the citationstyles.org
50
- frontpage), and we offer over 6750 free citation styles, covering thousands
51
- of scientific...","date_published":"2014-01-29T00:00:00Z","date_modified":"2014-01-29T00:00:00Z","authors":[{"url":null,"name":"Rintze
52
- M. Zelle"}],"image":null,"content_html":"<p>CSL has seen a lot of growth in
53
- recent years: more than 20 software products use CSL (see the <a href=\"http://citationstyles.org/\">citationstyles.org</a>
54
- frontpage), and we offer over 6750 free citation styles, covering thousands
55
- of scientific journals.</p>\n\n<p><img style=\"float: right;\" src=\"/assets/img/mendeley-csl-stickers.jpg\"
56
- width=\"320\" height=\"256\" /></p>\n\n<p>We could only have come this far
57
- with our great user community, and with a lot of institutional support from
58
- Mendeley, Papers, Zotero, and others.</p>\n\n<p><a href=\"http://www.mendeley.com/\">Mendeley</a>
59
- has been using CSL since their first release in 2008, and adopted Frank Bennett’s
60
- <a href=\"https://bitbucket.org/fbennett/citeproc-js/wiki/Home\">citeproc-js</a>
61
- CSL processor in 2010.\nThey have since moved away from simply using CSL to
62
- become one of our biggest contributors.\nCarles Pina of Mendeley helped us
63
- improve the central CSL style repository, and create CSL styles for 1500 Elsevier
64
- journals.\nMendeley also <a href=\"http://www.prnewswire.co.uk/news-releases/mendeley-teams-up-with-columbia-university-libraries-to-develop-a-citation-style-language-editor-through-125000-sloan-foundation-award-144578085.html\">collaborated</a>
65
- with Columbia University Libraries to created the <a href=\"http://editor.citationstyles.org/about/\">Visual
66
- CSL Editor</a>, which was funded by a Sloan Foundation Award and <a href=\"http://blog.mendeley.com/academic-features/make-your-citations-look-exactly-how-they-should-with-mendeleys-visual-citation-style-editor/\">released</a>
67
- in 2012.</p>\n\n<p>Now, Mendeley, together with Elsevier, stepped up once
68
- more, and made the first major financial contribution to the CSL project.\nWe
69
- received a $5000 donation, which we will use to cover project expenses and
70
- help ensure the long-term sustainability of CSL.\nMendeley is one of the most
71
- popular products to use CSL, and this level of involvement is crucial in helping
72
- us move CSL forward.\nWe hope others will follow Mendeley’s lead, and we look
73
- forward to continue improving CSL.</p>\n\n<p>In particular, we will collaborate
74
- with Zotero on their upcoming data model redesign, which should help us provide
75
- guidance to other projects on which fields each item type should carry and,
76
- among other things, improve support for primary and archival sources.\nWe
77
- also plan to adopt features from Frank Bennett’s <a href=\"http://citationstylist.org/\">Multilingual
78
- Zotero</a> into official CSL, such as better support for legal citations and
79
- citing items in multiple languages.\nWe’ll of course continue to maintain
80
- the project website and documentation, and handle style submissions to the
81
- repository.\nFinally, we’ll keep reaching out to publishers to further increase
82
- the number of journals covered by CSL styles.</p>","tags":[],"language":"en","blog_id":"prmb582","blog":{"id":"prmb582","title":"Citation
83
- Style Language","language":"en","favicon":null,"feed_url":"https://citationstyles.org/feed.xml","home_page_url":"https://citationstyles.org/","license":"https://creativecommons.org/licenses/by/4.0/legalcode","category":"Engineering
84
- and Technology"}}'
85
- recorded_at: Sun, 04 Jun 2023 10:18:36 GMT
86
- - request:
87
- method: get
88
- uri: https://rogue-scholar.org/api/posts/1jdkwod5
89
- body:
90
- encoding: UTF-8
91
- string: ''
92
- headers:
93
- Connection:
94
- - close
95
- Host:
96
- - rogue-scholar.org
97
- User-Agent:
98
- - http.rb/5.1.1
99
- response:
100
- status:
101
- code: 200
102
- message: OK
103
- headers:
104
- Age:
105
- - '0'
106
- Cache-Control:
107
- - public, max-age=0, must-revalidate
108
- Content-Length:
109
- - '3559'
110
- Content-Type:
111
- - application/json; charset=utf-8
112
- Date:
113
- - Sun, 04 Jun 2023 11:13:40 GMT
114
- Etag:
115
- - '"15ahqsuw1ek2q9"'
116
- Server:
117
- - Vercel
118
- Strict-Transport-Security:
119
- - max-age=63072000
120
- X-Matched-Path:
121
- - "/api/posts/[slug]"
122
- X-Vercel-Cache:
123
- - MISS
124
- X-Vercel-Id:
125
- - fra1::iad1::9bqqh-1685877219798-ee7c311b5c7e
126
- Connection:
127
- - close
128
- body:
129
- encoding: UTF-8
130
- string: '{"id":"https://citationstyles.org/2020/07/11/seeking-public-comment-on-CSL-1-0-2/","short_id":"1jdkwod5","url":"https://citationstyles.org/2020/07/11/seeking-public-comment-on-CSL-1-0-2/","title":"Seeking
131
- Public Comment on CSL 1.0.2 Release","summary":"Over the past few months,
132
- Citation Style Language developers have worked to address a backlog of feature
133
- requests. This work will be reflected in two upcoming releases. The first
134
- of these, 1.0.2, is slated...","date_published":"2020-07-11T00:00:00Z","date_modified":"2020-07-11T00:00:00Z","authors":[{"url":null,"name":"Sebastian
135
- Karcher"}],"image":null,"content_html":"<p>Over the past few months, Citation
136
- Style Language developers have worked to address a backlog of feature requests.
137
- This work will be reflected in two upcoming releases. The first of these,
138
- 1.0.2, is slated for release shortly. Its focus is on easy to implement, non-controversial
139
- additions, principally new item types, fields, and terms. We’re seeking public
140
- comment on the planned released from now until <strong>July 26, 2020, 12pm
141
- EDT</strong>.</p>\n\n<p>A non-technical summary of the release can be found
142
- in a <a href=\"https://docs.google.com/document/d/1wY1cOOamDYYh8VNW7h_uleqieBDGOa_LYsRiVdQy1RI/edit#heading=h.wsywjzy5t4j6\">google
143
- doc here</a>. For more technical details, you can follow the development on
144
- the <a href=\"https://github.com/orgs/citation-style-language/projects/3\">github
145
- project board</a>. We welcome feedback directly on the google doc, in specific
146
- github issues, or on our <a href=\"https://discourse.citationstyles.org/\">forums</a>.</p>\n\n<p>Tremendous
147
- thanks to Bruce D’Arcus, Denis Maier, and Brenton Wiernik, who did the bulk
148
- of the work of organizing proposals accumulated over the last 8 years and
149
- preparing the release.</p>\n\n<h2 id=\"previewing-csl-11\">Previewing CSL
150
- 1.1</h2>\n<p>CSL 1.1, slated for release later this year, will include more
151
- significant extensions of CSL functionality. While we’ll have a separate public
152
- comment period for this release, we’re happy for input on the ongoing discussions
153
- on github and the forums. In particular, we’re eager to hear from projects
154
- implementing CSL styles, both in a citeproc and in user-facing applications
155
- such as reference managers or citation formatters.</p>\n\n<p>This release
156
- will primarily add the following new features:</p>\n<ul>\n <li>Full support
157
- for narrative citation styles (“Like Doe (2018)”).</li>\n <li>Ability to
158
- specify more complex conditional logic.</li>\n <li>Ability to independently
159
- format subtitles and main titles.</li>\n <li>A new “related” attribute to
160
- express related reviewed and original items (still in discussion).</li>\n <li>Improvements
161
- to the CSL input format(s):\n <ul>\n <li>Adopting the new EDTF ISO
162
- standard, which offers full support for date ranges, seasons, uncertain and
163
- approximate qualifiers, and decades and centuries.</li>\n <li>A new “custom”
164
- property to add extension metadata.</li>\n <li>New related modelling
165
- to match the new style attribute (as above, still in discussion).</li>\n <li>An
166
- official YAML representation, which can be validated with the same JSON schemas.</li>\n </ul>\n </li>\n</ul>","tags":[],"language":"en","blog_id":"prmb582","blog":{"id":"prmb582","title":"Citation
167
- Style Language","language":"en","favicon":null,"feed_url":"https://citationstyles.org/feed.xml","home_page_url":"https://citationstyles.org/","license":"https://creativecommons.org/licenses/by/4.0/legalcode","category":"Engineering
168
- and Technology"}}'
169
- recorded_at: Sun, 04 Jun 2023 11:13:40 GMT
170
- recorded_with: VCR 6.1.0
@@ -1,163 +0,0 @@
1
- ---
2
- http_interactions:
3
- - request:
4
- method: get
5
- uri: https://rogue-scholar.org/api/posts/zkevlyd3
6
- body:
7
- encoding: UTF-8
8
- string: ''
9
- headers:
10
- Connection:
11
- - close
12
- Host:
13
- - rogue-scholar.org
14
- User-Agent:
15
- - http.rb/5.1.1
16
- response:
17
- status:
18
- code: 200
19
- message: OK
20
- headers:
21
- Age:
22
- - '0'
23
- Cache-Control:
24
- - public, max-age=0, must-revalidate
25
- Content-Length:
26
- - '11329'
27
- Content-Type:
28
- - application/json; charset=utf-8
29
- Date:
30
- - Sun, 04 Jun 2023 08:41:01 GMT
31
- Etag:
32
- - '"aszzwmkdb8oo"'
33
- Server:
34
- - Vercel
35
- Strict-Transport-Security:
36
- - max-age=63072000
37
- X-Matched-Path:
38
- - "/api/posts/[slug]"
39
- X-Vercel-Cache:
40
- - MISS
41
- X-Vercel-Id:
42
- - fra1::iad1::mp984-1685868057008-668fd6625f5a
43
- Connection:
44
- - close
45
- body:
46
- encoding: UTF-8
47
- string: '{"id":"https://wisspub.net/2023/05/23/eu-mitgliedstaaten-betonen-die-rolle-von-wissenschaftsgeleiteten-open-access-modellen-jenseits-von-apcs/","short_id":"zkevlyd3","url":"https://wisspub.net/2023/05/23/eu-mitgliedstaaten-betonen-die-rolle-von-wissenschaftsgeleiteten-open-access-modellen-jenseits-von-apcs/","title":"EU-Mitgliedstaaten
48
- betonen die Rolle von wissenschaftsgeleiteten Open-Access-Modellen jenseits
49
- von APCs","summary":"Die EU-Wissenschaftsministerien haben sich auf ihrer
50
- heutigen Sitzung in Brüssel unter dem Titel “Council conclusions on high-quality,
51
- transparent, open, trustworthy and equitable scholarly publishing” (PDF...","date_published":"2023-05-23T09:16:53Z","date_modified":"2023-05-23T09:16:53Z","authors":[{"url":"https://orcid.org/0000-0003-3334-2771","name":"Heinz
52
- Pampel"}],"image":null,"content_html":"\n<p>Die EU-Wissenschaftsministerien
53
- haben sich auf ihrer <a href=\"https://www.consilium.europa.eu/en/press/press-releases/2023/05/23/council-calls-for-transparent-equitable-and-open-access-to-scholarly-publications/\">heutigen
54
- Sitzung</a> in Brüssel unter dem Titel “Council conclusions on high-quality,
55
- transparent, open, trustworthy and equitable scholarly publishing” (<a href=\"https://data.consilium.europa.eu/doc/document/ST-8827-2023-INIT/en/pdf\">PDF
56
- der englischen Version</a>, <a href=\"https://data.consilium.europa.eu/doc/document/ST-8827-2023-INIT/de/pdf\">PDF
57
- der deutschen Version</a>) mit den aktuellen Herausforderungen des wissenschaftlichen
58
- Publikationswesens befasst.</p>\n\n\n\n<p>Bereits im Vorfeld der Sitzung der
59
- Wissenschaftsministerien wurden verschiedene Versionen der Erklärung öffentlich
60
- diskutiert (siehe z.B.<a href=\"https://sciencebusiness.net/news/Universities/leaked-eu-member-states-set-out-reform-scientific-publishing\">
61
- Science Business</a> und<a href=\"https://www.timeshighereducation.com/news/can-eu-make-parallel-publishing-system-work\">
62
- Times Higher Education</a>). Im Kern stand die Frage, inwiefern das EU-Papier
63
- den Fokus auf Finanzierungs- und Geschäftsmodelle abseits von Publikationsgebühren
64
- (Article Processing Charges, APCs) legt und ob sogar eine Abkehr von der Unterstützung
65
- dieses Modells durch die öffentliche Hand in Europa betont wird.</p>\n\n\n\n<p>Schweden
66
- hatte das Thema im Rahmen seiner EU-Ratspräsidentschaft augegriffen und bereits
67
- im <a href=\"https://wisspub.net/2023/02/10/eu-wissenschaftsministerien-erortern-open-science/\">Februar</a>
68
- in einem Hintergrund-Papier adressiert. Schon in diesem Briefing Paper wurde
69
- die Problematik steigender Preise für die wissenschaftlichen Fachinformation
70
- betont. </p>\n\n\n\n<p>In der jetzt verabschiedeten Version der Schlussfolgerungen
71
- die Forderung nach sofortigem Open Access für wissenschaftliche Publikationen,
72
- die im Rahmen der öffentlich geförderten Forschung entstehen, nochmals betont.
73
- Dieses Ziel wurde<a href=\"https://wisspub.net/2016/05/27/eu-und-g7-staaten-setzen-auf-open-science/\">
74
- bereits 2016</a> von den EU-Wissenschaftsministerien erhoben. Die Wissenschaftsminister:innen
75
- hatten damals einen Open-Access-Anteil von 100 % bis 2020 gefordert. Dieser
76
- Wert wurde bisher jedoch nicht erreicht. In Deutschland liegt der Open-Access-Anteil
77
- zum Beispiel bei <a href=\"https://open-access-monitor.de/\">63</a> Prozent,
78
- während die Niederlande im Publikationsjahr 2021 einen Anteil von <a href=\"https://www.openaccess.nl/en/in-the-netherlands/monitor\">82</a> Prozent
79
- erreichten.</p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"alignleft
80
- size-large is-resized\"><a href=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png\"><img
81
- loading=\"lazy\" data-attachment-id=\"20457\" data-permalink=\"https://wisspub.net/2023/05/23/eu-mitgliedstaaten-betonen-die-rolle-von-wissenschaftsgeleiteten-open-access-modellen-jenseits-von-apcs/bildschirmc2adfoto-2023-05-23-um-11-05-39/#main\"
82
- data-orig-file=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png\"
83
- data-orig-size=\"1512,2142\" data-comments-opened=\"1\" data-image-meta=\"{\"aperture\":\"0\",\"credit\":\"\",\"camera\":\"\",\"caption\":\"\",\"created_timestamp\":\"0\",\"copyright\":\"\",\"focal_length\":\"0\",\"iso\":\"0\",\"shutter_speed\":\"0\",\"title\":\"\",\"orientation\":\"0\"}\"
84
- data-image-title=\"bildschirmc2adfoto-2023-05-23-um-11.05.39\" data-image-description=\"\"
85
- data-image-caption=\"\" data-medium-file=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=212\"
86
- data-large-file=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=630\"
87
- src=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=723\"
88
- alt=\"\" class=\"wp-image-20457\" width=\"353\" height=\"500\" srcset=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=353
89
- 353w, https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=706
90
- 706w, https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=106
91
- 106w, https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=212
92
- 212w\" sizes=\"(max-width: 353px) 100vw, 353px\" /></a><figcaption class=\"wp-element-caption\"><em>“Council
93
- conclusions on high-quality, transparent, open, trustworthy and equitable
94
- scholarly publishing”</em></figcaption></figure></div>\n\n\n<p>Angesichts
95
- steigender Abonnementkosten und ähnlicher Entwicklungen im Bereich der Publikationsgebühren
96
- für Open Access und hybride Optionen betont das EU-Papier das Potenzial von
97
- Geschäfts- und Finanzierungsmodellen, die weder die Leser:innen noch die Autor:innen
98
- finanziell belasten und sich durch angemessene und transparente Preise auszeichnen
99
- (Punkt 6). Es wird beklagt, dass die steigenden Preise für wissenschaftliche
100
- Fachinformationen zu Ungleichheiten führen und die öffentliche Hand in Europa
101
- zum Nachteil der Forschung belasten (Punkt 5).</p>\n\n\n\n<p>Aufgrund dieser
102
- Kritik am kommerziellen Verlagswesen wird in zwei bemerkenswerten Punkten
103
- (6 und 7) die Bedeutung von nicht gewinnorientierten Open-Access-Modellen
104
- betont. Wortlaut:</p>\n\n\n\n<p>“The Council of the European Union [&#8230;]
105
- highlights the importance of not-for-profit, scholarly open access publishing
106
- models that do not charge fees to authors or readers and where authors can
107
- publish their work without funding/institutional eligibility criteria; notes
108
- the variety of models that do not depend on article processing charges or
109
- similar per-unit charges and stresses the importance of supporting the development
110
- of such models led by public research organisations; [&#8230;] stresses that
111
- it is essential to avoid situations where researchers are limited in their
112
- choice of publication channels due to financial capacities rather than quality
113
- criteria, and where access to research publications is restricted by paywalls”</p>\n\n\n\n<p>Zwar
114
- sind diese Unterstreichung und Betonung sicherlich nur ein kleiner Schritt
115
- auf dem Weg zur Gestaltung eines pluralistischen, transparenten und nachhaltigen
116
- Systems der digtialen Wissenschaftskommunikation. Sie kommen jedoch zu einem
117
- Zeitpunkt, zu dem die Kritik an dem Modell der Publikationsgebühren wächst.</p>\n\n\n\n<p>Erst
118
- kürzlich hat die Ivy Plus Libraries Confederation (IPLC) in den USA, als Zusammenschluss
119
- von Bibliotheken forschungsstarker Einrichtungen, das APC-Modell<a href=\"https://ivpluslibraries.org/2023/03/iplc-letter-to-the-office-of-science-technology-policy/\">
120
- deutlich kritisiert</a>. Die Bibliothekar:innen sehen die Gefahr, dass Publikationsgebühren
121
- Ungleichheit fördern und Forschende aus finanziell weniger gut ausgestatteten
122
- Regionen beim Open-Access-Publizieren benachteiligt werden. Sie charakterisieren
123
- APCs als eine Hürde bei der Publikation.</p>\n\n\n\n<p>Auch hat der öffentlichkeitswirksame
124
- <a href=\"https://www.nature.com/articles/d41586-023-01391-5\">Rücktritt</a>
125
- des Editorial Boards der Elsevier-Zeitschrift NeuroImage aufgrund steigender
126
- APCs den kritischen Blick auf das Geschäftsmodell gelenkt. Die zurückgetretenen
127
- Herausgebenden haben nun bei MIT Press ein neues Journal <a href=\"https://mitpress.mit.edu/the-mit-press-to-launch-open-access-journal-imaging-neuroscience/\">gegründet</a>,
128
- das niedrige APCs erhebt. Dieser Schritt zeigt, dass nicht APCs das Problem
129
- sein müssen, sondern vielmehr deren Preisgestaltung.</p>\n\n\n\n<p>Um die
130
- im obrigen Zitat formulierten Anliegen der EU-Staaten zu adressieren, soll
131
- die Koordinierung innerhalb der EU und mit globalen Partnern zur Unterstützung
132
- von Chancengleichheit im wissenschaftlichen Publizieren gefördert werden (Absatz
133
- 7). Hierzu sollen auch abgestimmte Finanzierungsstrategien entwickelt werden,
134
- um die Anzahl von not-for-profit open access multi-format scholarly publishing
135
- models in Europe with no costs for authors or readers&#8220; signifikant zu
136
- erhöhen (Absatz 11).</p>\n\n\n\n<p>Auch soll das Anliegen durch eine mögliche
137
- Beteiligung der EU-Mitgliedstaaten an Open Research Europe (ORE), der von
138
- der EU-Kommission finanzierten Publikationsplattform für Autor:innen aus den
139
- EU-Rahmenprogrammen, vorangetrieben werden (Absatz 15).&nbsp;</p>\n\n\n\n<p>In
140
- der <a href=\"https://www.consilium.europa.eu/de/press/press-releases/2023/05/23/council-calls-for-transparent-equitable-and-open-access-to-scholarly-publications/\">Pressemitteilung</a>
141
- werden weitere Themen der verabschiedeten Schlussfolgerungen augegriffen:&nbsp;</p>\n\n\n\n<p>“Some
142
- Member States have introduced secondary publication rights into their national
143
- copyright legislation, enabling open access to scholarly publications which
144
- involve public funds. The Council encourages national open access policies
145
- and guidelines to make scholarly publications immediately openly accessible
146
- under open licences. The conclusions acknowledge positive developments in
147
- terms of monitoring progress, like within the framework of the European Open
148
- Science Cloud (EOSC), and suggest including open science monitoring in the
149
- European Research Area monitoring mechanism.”</p>\n\n\n\n<p>Die Schlussfolgerungen
150
- können zweifellos als Stärkung des wissenschaftsgeleiteten Open-Access-Publizierens
151
- in akademischer Trägerschaft  interpretiert werden. Der eingeschlagene Kurs
152
- ist zu begrüßen. Um die bereits vielfältigen Open-Access-Publikationsangebote
153
- und -Verlage, die von wissenschaftlichen Einrichtungen betrieben oder gemeinsam
154
- (mit angemessenen und ohne APCs) finanziert werden, nachhaltig zu stärken,
155
- ist es erforderlich, kooperative Finanzierungsmodelle auf internationaler
156
- Ebene zu entwickeln und umzusetzen. Dafür sind, wie das Papier richtig betont,
157
- abgestimmte Förderaktivitäten erforderlich, die beispielsweise in Deutschland,
158
- komplementär zu DEAL, dem wissenschaftsgeleiteten Open-Access-Publizieren
159
- einen deutlichen Aufschwung geben.</p>\n","tags":["Open Access","Open Access
160
- Transformation","Open Science","EU"],"language":"de","blog_id":"34zkv26","blog":{"id":"34zkv26","title":"wisspub.net","language":"de","favicon":null,"feed_url":"https://wisspub.net/feed/atom/","home_page_url":"https://wisspub.net/","license":"https://creativecommons.org/licenses/by/4.0/legalcode","category":"Engineering
161
- and Technology"}}'
162
- recorded_at: Sun, 04 Jun 2023 08:41:01 GMT
163
- recorded_with: VCR 6.1.0