commonmeta-ruby 3.2.0 → 3.2.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (36) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +1 -1
  3. data/bin/commonmeta +1 -1
  4. data/lib/commonmeta/cli.rb +7 -0
  5. data/lib/commonmeta/metadata_utils.rb +2 -2
  6. data/lib/commonmeta/readers/{json_post_reader.rb → json_feed_reader.rb} +16 -4
  7. data/lib/commonmeta/utils.rb +6 -2
  8. data/lib/commonmeta/version.rb +1 -1
  9. data/spec/cli_spec.rb +8 -0
  10. data/spec/fixtures/vcr_cassettes/Commonmeta_CLI/json_feed/blog_post.yml +360 -0
  11. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed/citation_style_language.yml +360 -0
  12. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed/citation_style_language_blog.yml +360 -0
  13. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed/front-matter_blog.yml +1034 -0
  14. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed/upstream.yml +2438 -0
  15. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed/upstream_blog.yml +2438 -0
  16. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/blogger_post.yml +94 -0
  17. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_with_doi.yml +117 -0
  18. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/jekyll_post.yml +87 -0
  19. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/wordpress_post.yml +163 -0
  20. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_metadata/blogger_post.yml +141 -0
  21. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_metadata/ghost_post_with_doi.yml +164 -0
  22. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_metadata/jekyll_post.yml +134 -0
  23. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_metadata/wordpress_post.yml +210 -0
  24. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_post_metadata/blogger_post.yml +47 -0
  25. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_post_metadata/ghost_post_with_doi.yml +47 -0
  26. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_post_metadata/jekyll_post.yml +47 -0
  27. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_post_metadata/wordpress_post.yml +47 -0
  28. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/json_feed_url/front-matter_blog.yml +221 -0
  29. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_feed_item_from_rogue_scholar_with_doi.yml +163 -0
  30. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_feed_item_from_upstream_blog.yml +243 -0
  31. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_post_from_rogue_scholar_with_doi.yml +47 -0
  32. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_post_from_upstream_blog.yml +47 -0
  33. data/spec/readers/{json_post_reader_spec.rb → json_feed_reader_spec.rb} +23 -2
  34. data/spec/utils_spec.rb +8 -0
  35. data/spec/writers/crossref_xml_writer_spec.rb +2 -2
  36. metadata +20 -3
@@ -0,0 +1,164 @@
1
+ ---
2
+ http_interactions:
3
+ - request:
4
+ method: get
5
+ uri: https://rogue-scholar.org/api/blogs/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: 308
19
+ message: Permanent Redirect
20
+ headers:
21
+ Cache-Control:
22
+ - public, max-age=0, must-revalidate
23
+ Content-Type:
24
+ - text/plain
25
+ Date:
26
+ - Sun, 04 Jun 2023 13:19:22 GMT
27
+ Location:
28
+ - "/api/blogs/https:/rogue-scholar.org/api/posts/1jgo8yel"
29
+ Refresh:
30
+ - 0;url=/api/blogs/https:/rogue-scholar.org/api/posts/1jgo8yel
31
+ Server:
32
+ - Vercel
33
+ Strict-Transport-Security:
34
+ - max-age=63072000
35
+ X-Vercel-Cache:
36
+ - MISS
37
+ X-Vercel-Id:
38
+ - fra1::6rk6m-1685884762980-dd5e259acd6c
39
+ Connection:
40
+ - close
41
+ Transfer-Encoding:
42
+ - chunked
43
+ body:
44
+ encoding: ASCII-8BIT
45
+ string: 'Redirecting to /api/blogs/https:/rogue-scholar.org/api/posts/1jgo8yel
46
+ (308)
47
+
48
+ '
49
+ recorded_at: Sun, 04 Jun 2023 13:19:22 GMT
50
+ - request:
51
+ method: get
52
+ uri: https://rogue-scholar.org/api/posts/1jgo8yel
53
+ body:
54
+ encoding: UTF-8
55
+ string: ''
56
+ headers:
57
+ Connection:
58
+ - close
59
+ Host:
60
+ - rogue-scholar.org
61
+ User-Agent:
62
+ - http.rb/5.1.1
63
+ response:
64
+ status:
65
+ code: 200
66
+ message: OK
67
+ headers:
68
+ Age:
69
+ - '0'
70
+ Cache-Control:
71
+ - public, max-age=0, must-revalidate
72
+ Content-Length:
73
+ - '6894'
74
+ Content-Type:
75
+ - application/json; charset=utf-8
76
+ Date:
77
+ - Sun, 04 Jun 2023 13:22:55 GMT
78
+ Etag:
79
+ - '"r1h98s95tn5bh"'
80
+ Server:
81
+ - Vercel
82
+ Strict-Transport-Security:
83
+ - max-age=63072000
84
+ X-Matched-Path:
85
+ - "/api/posts/[slug]"
86
+ X-Vercel-Cache:
87
+ - MISS
88
+ X-Vercel-Id:
89
+ - fra1::iad1::x6k7h-1685884975263-355ba84ed0b5
90
+ Connection:
91
+ - close
92
+ body:
93
+ encoding: UTF-8
94
+ string: '{"id":"https://doi.org/10.53731/4nwxn-frt36","short_id":"1jgo8yel","url":"https://blog.front-matter.io/posts/does-it-compose/","title":"Does
95
+ it compose?","summary":"One question I have increasingly asked myself in the
96
+ past few years. Meaning Can I run this open source software using Docker containers
97
+ 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
98
+ 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":"
99
+ <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
100
+ question I have increasingly asked myself in the past few years. Meaning </p><blockquote>Can
101
+ I run this open source software  using Docker containers and a Docker Compose
102
+ file?</blockquote><p>As the Docker project <a href=\"https://snyk.io/blog/the-docker-project-turns-10/\">turned
103
+ ten this spring</a>, it has become standard practice to distribute open source
104
+ software via Docker images and to provide a <a href=\"https://docs.docker.com/compose/\">Docker
105
+ Compose</a> file to run the software together with other dependencies. The
106
+ <a href=\"https://github.com/docker/awesome-compose\">Awesome Compose</a>
107
+ project has collected many examples, and all you need is a <code>docker-compose.yml</code>file
108
+ and a recent installation of Docker, e.g. <a href=\"https://www.docker.com/products/docker-desktop/\">Docker
109
+ Desktop</a>. Be aware that Docker Compose has evolved over the years. It started
110
+ out as a dedicated Python application but was later integrated into the Docker
111
+ application (written in Go) as Compose V2.</p><p>Docker and Docker Compose
112
+ allow you to run pretty complex applications without first addressing a long
113
+ list of requirements (which might conflict with other software you have installed),
114
+ or needing a long and complex build step where many things can go wrong. For
115
+ example a self-hosted instance of Supabase (a hosted Postgres database with
116
+ additional features) that I installed last week following <a href=\"https://supabase.com/docs/guides/self-hosting/docker\">these
117
+ instructions</a>.</p><p>An important open source project that I am involved
118
+ in is <a href=\"https://inveniordm.docs.cern.ch/\">InvenioRDM</a>, the turn-key
119
+ research data management repository. InvenioRDM started in 2019, with a first
120
+ production-suitable version in August 2021, and the <a href=\"https://inveniosoftware.org/products/rdm/#status\">next
121
+ major goal </a>is to have the large and popular <a href=\"https://zenodo.org/\">Zenodo</a>
122
+ repository running on top of InvenioRDM. Zenodo <a href=\"https://blog.zenodo.org/2023/05/08/2023-05-08-10years/\">turned
123
+ ten last week</a>, a few weeks after Docker. Interestingly, my personal tenth
124
+ anniversary was last year in May as I became a full-time software developer
125
+ and left academic medicine as a medical doctor treating cancer patients in
126
+ <a href=\"https://doi.org/10.53731/r294649-6f79289-8cw2j\">May 2012</a>.</p><p>Unfortunately,
127
+ InvenioRDM \"doesn''t compose\" yet. It is very close, but there are no ready-made
128
+ Docker images to download, and the <a href=\"https://inveniordm.docs.cern.ch/install/\">installation
129
+ instructions</a> start with installing a Python command-line tool (invenio-cli).
130
+ So if you have 1-2 hours to play with InvenioRDM and get a first impression,
131
+ there is no official solution from the InvenioRDM project yet. For this reason,
132
+ I started the <a href=\"https://github.com/front-matter/docker-invenio-rdm\">docker-invenio-rdm</a>
133
+ repository on Github. It contains a Docker Compose file that uses pre-built
134
+ Docker images, and using that file with a <code>docker compose up</code>command
135
+ on your local computer should give you a running InvenioRDM within 15 minutes:</p><figure
136
+ 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\"
137
+ 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
138
+ 600w, https://blog.front-matter.io/content/images/size/w1000/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
139
+ 1000w, https://blog.front-matter.io/content/images/size/w1600/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
140
+ 1600w, https://blog.front-matter.io/content/images/2023/05/Bildschirmfoto-2023-05-11-um-10.37.55.png
141
+ 2193w\" sizes=\"(min-width: 720px) 720px\"></figure><p>I started this recently
142
+ and obviously want to move forward in two directions:</p><ul><li>fine-tune
143
+ the initial configuration to provide a great initial experience with InvenioRDM,
144
+ e.g. making it easy to <a href=\"https://inveniordm.docs.cern.ch/develop/topics/theming/\">theme</a>
145
+ the InvenioRDM instance</li><li>make this an official part of the InvenioRDM
146
+ project, extending the <a href=\"https://github.com/inveniosoftware/docker-invenio\">docker-invenio</a>
147
+ GitHub repository that provides Docker base images for InvenioRDM and other
148
+ projects using the Invenio software.</li></ul><p>But of course, Docker Compose
149
+ is not the answer to all questions regarding running Docker-based infrastructure.
150
+ For production environments, most people shy away from using Docker Compose.
151
+ The reasons for that and the alternatives will be the topic of a future blog
152
+ post (spoiler: there is exciting news).</p><p>Docker Compose also needs more
153
+ work to be set up correctly for development environments. It is a common practice
154
+ and a workflow I used while working at DataCite (where we launched Docker-based
155
+ infrastructure in 2016), but for now, the easiest way to set up InvenioRDM
156
+ development environments is using the <a href=\"https://inveniordm.docs.cern.ch/install/\">invenio-cli
157
+ tool with a local development environment</a>.</p><p>Please reach out to me
158
+ with feedback on running Docker Compose for InvenioRDM (use the <a href=\"https://github.com/front-matter/docker-invenio-rdm/discussions\">discussions</a>
159
+ feature in the GitHub repo), or if you have questions about running InvenioRDM
160
+ in production.</p> ","tags":["News"],"language":"en","blog_id":"f0m0e38","blog":{"id":"f0m0e38","title":"Front
161
+ 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
162
+ and Technology"}}'
163
+ recorded_at: Sun, 04 Jun 2023 13:22:55 GMT
164
+ recorded_with: VCR 6.1.0
@@ -0,0 +1,134 @@
1
+ ---
2
+ http_interactions:
3
+ - request:
4
+ method: get
5
+ uri: https://rogue-scholar.org/api/blogs/https://rogue-scholar.org/api/posts/1jdkwod5
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: 308
19
+ message: Permanent Redirect
20
+ headers:
21
+ Cache-Control:
22
+ - public, max-age=0, must-revalidate
23
+ Content-Type:
24
+ - text/plain
25
+ Date:
26
+ - Sun, 04 Jun 2023 13:19:22 GMT
27
+ Location:
28
+ - "/api/blogs/https:/rogue-scholar.org/api/posts/1jdkwod5"
29
+ Refresh:
30
+ - 0;url=/api/blogs/https:/rogue-scholar.org/api/posts/1jdkwod5
31
+ Server:
32
+ - Vercel
33
+ Strict-Transport-Security:
34
+ - max-age=63072000
35
+ X-Vercel-Cache:
36
+ - MISS
37
+ X-Vercel-Id:
38
+ - fra1::b86qp-1685884762624-ef647a1e8361
39
+ Connection:
40
+ - close
41
+ Transfer-Encoding:
42
+ - chunked
43
+ body:
44
+ encoding: ASCII-8BIT
45
+ string: 'Redirecting to /api/blogs/https:/rogue-scholar.org/api/posts/1jdkwod5
46
+ (308)
47
+
48
+ '
49
+ recorded_at: Sun, 04 Jun 2023 13:19:22 GMT
50
+ - request:
51
+ method: get
52
+ uri: https://rogue-scholar.org/api/posts/1jdkwod5
53
+ body:
54
+ encoding: UTF-8
55
+ string: ''
56
+ headers:
57
+ Connection:
58
+ - close
59
+ Host:
60
+ - rogue-scholar.org
61
+ User-Agent:
62
+ - http.rb/5.1.1
63
+ response:
64
+ status:
65
+ code: 200
66
+ message: OK
67
+ headers:
68
+ Age:
69
+ - '0'
70
+ Cache-Control:
71
+ - public, max-age=0, must-revalidate
72
+ Content-Length:
73
+ - '3559'
74
+ Content-Type:
75
+ - application/json; charset=utf-8
76
+ Date:
77
+ - Sun, 04 Jun 2023 13:22:56 GMT
78
+ Etag:
79
+ - '"15ahqsuw1ek2q9"'
80
+ Server:
81
+ - Vercel
82
+ Strict-Transport-Security:
83
+ - max-age=63072000
84
+ X-Matched-Path:
85
+ - "/api/posts/[slug]"
86
+ X-Vercel-Cache:
87
+ - MISS
88
+ X-Vercel-Id:
89
+ - fra1::iad1::4g2bf-1685884976137-f69c39b47476
90
+ Connection:
91
+ - close
92
+ body:
93
+ encoding: UTF-8
94
+ 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
95
+ Public Comment on CSL 1.0.2 Release","summary":"Over the past few months,
96
+ Citation Style Language developers have worked to address a backlog of feature
97
+ requests. This work will be reflected in two upcoming releases. The first
98
+ 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
99
+ Karcher"}],"image":null,"content_html":"<p>Over the past few months, Citation
100
+ Style Language developers have worked to address a backlog of feature requests.
101
+ This work will be reflected in two upcoming releases. The first of these,
102
+ 1.0.2, is slated for release shortly. Its focus is on easy to implement, non-controversial
103
+ additions, principally new item types, fields, and terms. We’re seeking public
104
+ comment on the planned released from now until <strong>July 26, 2020, 12pm
105
+ EDT</strong>.</p>\n\n<p>A non-technical summary of the release can be found
106
+ in a <a href=\"https://docs.google.com/document/d/1wY1cOOamDYYh8VNW7h_uleqieBDGOa_LYsRiVdQy1RI/edit#heading=h.wsywjzy5t4j6\">google
107
+ doc here</a>. For more technical details, you can follow the development on
108
+ the <a href=\"https://github.com/orgs/citation-style-language/projects/3\">github
109
+ project board</a>. We welcome feedback directly on the google doc, in specific
110
+ github issues, or on our <a href=\"https://discourse.citationstyles.org/\">forums</a>.</p>\n\n<p>Tremendous
111
+ thanks to Bruce D’Arcus, Denis Maier, and Brenton Wiernik, who did the bulk
112
+ of the work of organizing proposals accumulated over the last 8 years and
113
+ preparing the release.</p>\n\n<h2 id=\"previewing-csl-11\">Previewing CSL
114
+ 1.1</h2>\n<p>CSL 1.1, slated for release later this year, will include more
115
+ significant extensions of CSL functionality. While we’ll have a separate public
116
+ comment period for this release, we’re happy for input on the ongoing discussions
117
+ on github and the forums. In particular, we’re eager to hear from projects
118
+ implementing CSL styles, both in a citeproc and in user-facing applications
119
+ such as reference managers or citation formatters.</p>\n\n<p>This release
120
+ will primarily add the following new features:</p>\n<ul>\n <li>Full support
121
+ for narrative citation styles (“Like Doe (2018)”).</li>\n <li>Ability to
122
+ specify more complex conditional logic.</li>\n <li>Ability to independently
123
+ format subtitles and main titles.</li>\n <li>A new “related” attribute to
124
+ express related reviewed and original items (still in discussion).</li>\n <li>Improvements
125
+ to the CSL input format(s):\n <ul>\n <li>Adopting the new EDTF ISO
126
+ standard, which offers full support for date ranges, seasons, uncertain and
127
+ approximate qualifiers, and decades and centuries.</li>\n <li>A new “custom”
128
+ property to add extension metadata.</li>\n <li>New related modelling
129
+ to match the new style attribute (as above, still in discussion).</li>\n <li>An
130
+ 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
131
+ 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
132
+ and Technology"}}'
133
+ recorded_at: Sun, 04 Jun 2023 13:22:56 GMT
134
+ recorded_with: VCR 6.1.0
@@ -0,0 +1,210 @@
1
+ ---
2
+ http_interactions:
3
+ - request:
4
+ method: get
5
+ uri: https://rogue-scholar.org/api/blogs/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: 308
19
+ message: Permanent Redirect
20
+ headers:
21
+ Cache-Control:
22
+ - public, max-age=0, must-revalidate
23
+ Content-Type:
24
+ - text/plain
25
+ Date:
26
+ - Sun, 04 Jun 2023 13:19:23 GMT
27
+ Location:
28
+ - "/api/blogs/https:/rogue-scholar.org/api/posts/zkevlyd3"
29
+ Refresh:
30
+ - 0;url=/api/blogs/https:/rogue-scholar.org/api/posts/zkevlyd3
31
+ Server:
32
+ - Vercel
33
+ Strict-Transport-Security:
34
+ - max-age=63072000
35
+ X-Vercel-Cache:
36
+ - MISS
37
+ X-Vercel-Id:
38
+ - fra1::ms7l2-1685884763155-405b12e832e6
39
+ Connection:
40
+ - close
41
+ Transfer-Encoding:
42
+ - chunked
43
+ body:
44
+ encoding: ASCII-8BIT
45
+ string: 'Redirecting to /api/blogs/https:/rogue-scholar.org/api/posts/zkevlyd3
46
+ (308)
47
+
48
+ '
49
+ recorded_at: Sun, 04 Jun 2023 13:19:23 GMT
50
+ - request:
51
+ method: get
52
+ uri: https://rogue-scholar.org/api/posts/zkevlyd3
53
+ body:
54
+ encoding: UTF-8
55
+ string: ''
56
+ headers:
57
+ Connection:
58
+ - close
59
+ Host:
60
+ - rogue-scholar.org
61
+ User-Agent:
62
+ - http.rb/5.1.1
63
+ response:
64
+ status:
65
+ code: 200
66
+ message: OK
67
+ headers:
68
+ Age:
69
+ - '0'
70
+ Cache-Control:
71
+ - public, max-age=0, must-revalidate
72
+ Content-Length:
73
+ - '11329'
74
+ Content-Type:
75
+ - application/json; charset=utf-8
76
+ Date:
77
+ - Sun, 04 Jun 2023 13:22:54 GMT
78
+ Etag:
79
+ - '"aszzwmkdb8oo"'
80
+ Server:
81
+ - Vercel
82
+ Strict-Transport-Security:
83
+ - max-age=63072000
84
+ X-Matched-Path:
85
+ - "/api/posts/[slug]"
86
+ X-Vercel-Cache:
87
+ - MISS
88
+ X-Vercel-Id:
89
+ - fra1::iad1::gg2gd-1685884974165-ff7502004c05
90
+ Connection:
91
+ - close
92
+ body:
93
+ encoding: UTF-8
94
+ 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
95
+ betonen die Rolle von wissenschaftsgeleiteten Open-Access-Modellen jenseits
96
+ von APCs","summary":"Die EU-Wissenschaftsministerien haben sich auf ihrer
97
+ heutigen Sitzung in Brüssel unter dem Titel “Council conclusions on high-quality,
98
+ 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
99
+ Pampel"}],"image":null,"content_html":"\n<p>Die EU-Wissenschaftsministerien
100
+ 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
101
+ Sitzung</a> in Brüssel unter dem Titel “Council conclusions on high-quality,
102
+ transparent, open, trustworthy and equitable scholarly publishing” (<a href=\"https://data.consilium.europa.eu/doc/document/ST-8827-2023-INIT/en/pdf\">PDF
103
+ der englischen Version</a>, <a href=\"https://data.consilium.europa.eu/doc/document/ST-8827-2023-INIT/de/pdf\">PDF
104
+ der deutschen Version</a>) mit den aktuellen Herausforderungen des wissenschaftlichen
105
+ Publikationswesens befasst.</p>\n\n\n\n<p>Bereits im Vorfeld der Sitzung der
106
+ Wissenschaftsministerien wurden verschiedene Versionen der Erklärung öffentlich
107
+ diskutiert (siehe z.B.<a href=\"https://sciencebusiness.net/news/Universities/leaked-eu-member-states-set-out-reform-scientific-publishing\">
108
+ Science Business</a> und<a href=\"https://www.timeshighereducation.com/news/can-eu-make-parallel-publishing-system-work\">
109
+ Times Higher Education</a>). Im Kern stand die Frage, inwiefern das EU-Papier
110
+ den Fokus auf Finanzierungs- und Geschäftsmodelle abseits von Publikationsgebühren
111
+ (Article Processing Charges, APCs) legt und ob sogar eine Abkehr von der Unterstützung
112
+ dieses Modells durch die öffentliche Hand in Europa betont wird.</p>\n\n\n\n<p>Schweden
113
+ hatte das Thema im Rahmen seiner EU-Ratspräsidentschaft augegriffen und bereits
114
+ im <a href=\"https://wisspub.net/2023/02/10/eu-wissenschaftsministerien-erortern-open-science/\">Februar</a>
115
+ in einem Hintergrund-Papier adressiert. Schon in diesem Briefing Paper wurde
116
+ die Problematik steigender Preise für die wissenschaftlichen Fachinformation
117
+ betont. </p>\n\n\n\n<p>In der jetzt verabschiedeten Version der Schlussfolgerungen
118
+ die Forderung nach sofortigem Open Access für wissenschaftliche Publikationen,
119
+ die im Rahmen der öffentlich geförderten Forschung entstehen, nochmals betont.
120
+ Dieses Ziel wurde<a href=\"https://wisspub.net/2016/05/27/eu-und-g7-staaten-setzen-auf-open-science/\">
121
+ bereits 2016</a> von den EU-Wissenschaftsministerien erhoben. Die Wissenschaftsminister:innen
122
+ hatten damals einen Open-Access-Anteil von 100 % bis 2020 gefordert. Dieser
123
+ Wert wurde bisher jedoch nicht erreicht. In Deutschland liegt der Open-Access-Anteil
124
+ zum Beispiel bei <a href=\"https://open-access-monitor.de/\">63</a> Prozent,
125
+ während die Niederlande im Publikationsjahr 2021 einen Anteil von <a href=\"https://www.openaccess.nl/en/in-the-netherlands/monitor\">82</a> Prozent
126
+ erreichten.</p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"alignleft
127
+ size-large is-resized\"><a href=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png\"><img
128
+ 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\"
129
+ data-orig-file=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png\"
130
+ 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\"}\"
131
+ data-image-title=\"bildschirmc2adfoto-2023-05-23-um-11.05.39\" data-image-description=\"\"
132
+ data-image-caption=\"\" data-medium-file=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=212\"
133
+ data-large-file=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=630\"
134
+ src=\"https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=723\"
135
+ 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
136
+ 353w, https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=706
137
+ 706w, https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=106
138
+ 106w, https://wisspub.files.wordpress.com/2023/05/bildschirmc2adfoto-2023-05-23-um-11.05.39.png?w=212
139
+ 212w\" sizes=\"(max-width: 353px) 100vw, 353px\" /></a><figcaption class=\"wp-element-caption\"><em>“Council
140
+ conclusions on high-quality, transparent, open, trustworthy and equitable
141
+ scholarly publishing”</em></figcaption></figure></div>\n\n\n<p>Angesichts
142
+ steigender Abonnementkosten und ähnlicher Entwicklungen im Bereich der Publikationsgebühren
143
+ für Open Access und hybride Optionen betont das EU-Papier das Potenzial von
144
+ Geschäfts- und Finanzierungsmodellen, die weder die Leser:innen noch die Autor:innen
145
+ finanziell belasten und sich durch angemessene und transparente Preise auszeichnen
146
+ (Punkt 6). Es wird beklagt, dass die steigenden Preise für wissenschaftliche
147
+ Fachinformationen zu Ungleichheiten führen und die öffentliche Hand in Europa
148
+ zum Nachteil der Forschung belasten (Punkt 5).</p>\n\n\n\n<p>Aufgrund dieser
149
+ Kritik am kommerziellen Verlagswesen wird in zwei bemerkenswerten Punkten
150
+ (6 und 7) die Bedeutung von nicht gewinnorientierten Open-Access-Modellen
151
+ betont. Wortlaut:</p>\n\n\n\n<p>“The Council of the European Union [&#8230;]
152
+ highlights the importance of not-for-profit, scholarly open access publishing
153
+ models that do not charge fees to authors or readers and where authors can
154
+ publish their work without funding/institutional eligibility criteria; notes
155
+ the variety of models that do not depend on article processing charges or
156
+ similar per-unit charges and stresses the importance of supporting the development
157
+ of such models led by public research organisations; [&#8230;] stresses that
158
+ it is essential to avoid situations where researchers are limited in their
159
+ choice of publication channels due to financial capacities rather than quality
160
+ criteria, and where access to research publications is restricted by paywalls”</p>\n\n\n\n<p>Zwar
161
+ sind diese Unterstreichung und Betonung sicherlich nur ein kleiner Schritt
162
+ auf dem Weg zur Gestaltung eines pluralistischen, transparenten und nachhaltigen
163
+ Systems der digtialen Wissenschaftskommunikation. Sie kommen jedoch zu einem
164
+ Zeitpunkt, zu dem die Kritik an dem Modell der Publikationsgebühren wächst.</p>\n\n\n\n<p>Erst
165
+ kürzlich hat die Ivy Plus Libraries Confederation (IPLC) in den USA, als Zusammenschluss
166
+ von Bibliotheken forschungsstarker Einrichtungen, das APC-Modell<a href=\"https://ivpluslibraries.org/2023/03/iplc-letter-to-the-office-of-science-technology-policy/\">
167
+ deutlich kritisiert</a>. Die Bibliothekar:innen sehen die Gefahr, dass Publikationsgebühren
168
+ Ungleichheit fördern und Forschende aus finanziell weniger gut ausgestatteten
169
+ Regionen beim Open-Access-Publizieren benachteiligt werden. Sie charakterisieren
170
+ APCs als eine Hürde bei der Publikation.</p>\n\n\n\n<p>Auch hat der öffentlichkeitswirksame
171
+ <a href=\"https://www.nature.com/articles/d41586-023-01391-5\">Rücktritt</a>
172
+ des Editorial Boards der Elsevier-Zeitschrift NeuroImage aufgrund steigender
173
+ APCs den kritischen Blick auf das Geschäftsmodell gelenkt. Die zurückgetretenen
174
+ 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>,
175
+ das niedrige APCs erhebt. Dieser Schritt zeigt, dass nicht APCs das Problem
176
+ sein müssen, sondern vielmehr deren Preisgestaltung.</p>\n\n\n\n<p>Um die
177
+ im obrigen Zitat formulierten Anliegen der EU-Staaten zu adressieren, soll
178
+ die Koordinierung innerhalb der EU und mit globalen Partnern zur Unterstützung
179
+ von Chancengleichheit im wissenschaftlichen Publizieren gefördert werden (Absatz
180
+ 7). Hierzu sollen auch abgestimmte Finanzierungsstrategien entwickelt werden,
181
+ um die Anzahl von not-for-profit open access multi-format scholarly publishing
182
+ models in Europe with no costs for authors or readers&#8220; signifikant zu
183
+ erhöhen (Absatz 11).</p>\n\n\n\n<p>Auch soll das Anliegen durch eine mögliche
184
+ Beteiligung der EU-Mitgliedstaaten an Open Research Europe (ORE), der von
185
+ der EU-Kommission finanzierten Publikationsplattform für Autor:innen aus den
186
+ EU-Rahmenprogrammen, vorangetrieben werden (Absatz 15).&nbsp;</p>\n\n\n\n<p>In
187
+ 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>
188
+ werden weitere Themen der verabschiedeten Schlussfolgerungen augegriffen:&nbsp;</p>\n\n\n\n<p>“Some
189
+ Member States have introduced secondary publication rights into their national
190
+ copyright legislation, enabling open access to scholarly publications which
191
+ involve public funds. The Council encourages national open access policies
192
+ and guidelines to make scholarly publications immediately openly accessible
193
+ under open licences. The conclusions acknowledge positive developments in
194
+ terms of monitoring progress, like within the framework of the European Open
195
+ Science Cloud (EOSC), and suggest including open science monitoring in the
196
+ European Research Area monitoring mechanism.”</p>\n\n\n\n<p>Die Schlussfolgerungen
197
+ können zweifellos als Stärkung des wissenschaftsgeleiteten Open-Access-Publizierens
198
+ in akademischer Trägerschaft  interpretiert werden. Der eingeschlagene Kurs
199
+ ist zu begrüßen. Um die bereits vielfältigen Open-Access-Publikationsangebote
200
+ und -Verlage, die von wissenschaftlichen Einrichtungen betrieben oder gemeinsam
201
+ (mit angemessenen und ohne APCs) finanziert werden, nachhaltig zu stärken,
202
+ ist es erforderlich, kooperative Finanzierungsmodelle auf internationaler
203
+ Ebene zu entwickeln und umzusetzen. Dafür sind, wie das Papier richtig betont,
204
+ abgestimmte Förderaktivitäten erforderlich, die beispielsweise in Deutschland,
205
+ komplementär zu DEAL, dem wissenschaftsgeleiteten Open-Access-Publizieren
206
+ einen deutlichen Aufschwung geben.</p>\n","tags":["Open Access","Open Access
207
+ 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
208
+ and Technology"}}'
209
+ recorded_at: Sun, 04 Jun 2023 13:22:54 GMT
210
+ recorded_with: VCR 6.1.0
@@ -91,4 +91,51 @@ http_interactions:
91
91
  with <a href=\"https://stackedit.io/\">StackEdit</a>.</p>\n</blockquote>","tags":[],"language":"en","blog_id":"tyfqw20","blog":{"id":"tyfqw20","title":"iPhylo","language":"en","favicon":null,"feed_url":"https://iphylo.blogspot.com/feeds/posts/default?alt=rss","home_page_url":"https://iphylo.blogspot.com/","license":"https://creativecommons.org/licenses/by/4.0/legalcode","category":"Natural
92
92
  Sciences"}}'
93
93
  recorded_at: Sun, 04 Jun 2023 11:24:19 GMT
94
+ - request:
95
+ method: get
96
+ uri: https://rogue-scholar.org/api/blogs/https://rogue-scholar.org/api/posts/1jgo59el
97
+ body:
98
+ encoding: UTF-8
99
+ string: ''
100
+ headers:
101
+ Connection:
102
+ - close
103
+ Host:
104
+ - rogue-scholar.org
105
+ User-Agent:
106
+ - http.rb/5.1.1
107
+ response:
108
+ status:
109
+ code: 308
110
+ message: Permanent Redirect
111
+ headers:
112
+ Cache-Control:
113
+ - public, max-age=0, must-revalidate
114
+ Content-Type:
115
+ - text/plain
116
+ Date:
117
+ - Sun, 04 Jun 2023 13:17:11 GMT
118
+ Location:
119
+ - "/api/blogs/https:/rogue-scholar.org/api/posts/1jgo59el"
120
+ Refresh:
121
+ - 0;url=/api/blogs/https:/rogue-scholar.org/api/posts/1jgo59el
122
+ Server:
123
+ - Vercel
124
+ Strict-Transport-Security:
125
+ - max-age=63072000
126
+ X-Vercel-Cache:
127
+ - MISS
128
+ X-Vercel-Id:
129
+ - fra1::rkkzk-1685884631381-9f6a9ad54465
130
+ Connection:
131
+ - close
132
+ Transfer-Encoding:
133
+ - chunked
134
+ body:
135
+ encoding: ASCII-8BIT
136
+ string: 'Redirecting to /api/blogs/https:/rogue-scholar.org/api/posts/1jgo59el
137
+ (308)
138
+
139
+ '
140
+ recorded_at: Sun, 04 Jun 2023 13:17:11 GMT
94
141
  recorded_with: VCR 6.1.0
@@ -114,4 +114,51 @@ http_interactions:
114
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
115
  and Technology"}}'
116
116
  recorded_at: Sun, 04 Jun 2023 11:24:21 GMT
117
+ - request:
118
+ method: get
119
+ uri: https://rogue-scholar.org/api/blogs/https://rogue-scholar.org/api/posts/1jgo8yel
120
+ body:
121
+ encoding: UTF-8
122
+ string: ''
123
+ headers:
124
+ Connection:
125
+ - close
126
+ Host:
127
+ - rogue-scholar.org
128
+ User-Agent:
129
+ - http.rb/5.1.1
130
+ response:
131
+ status:
132
+ code: 308
133
+ message: Permanent Redirect
134
+ headers:
135
+ Cache-Control:
136
+ - public, max-age=0, must-revalidate
137
+ Content-Type:
138
+ - text/plain
139
+ Date:
140
+ - Sun, 04 Jun 2023 13:17:11 GMT
141
+ Location:
142
+ - "/api/blogs/https:/rogue-scholar.org/api/posts/1jgo8yel"
143
+ Refresh:
144
+ - 0;url=/api/blogs/https:/rogue-scholar.org/api/posts/1jgo8yel
145
+ Server:
146
+ - Vercel
147
+ Strict-Transport-Security:
148
+ - max-age=63072000
149
+ X-Vercel-Cache:
150
+ - MISS
151
+ X-Vercel-Id:
152
+ - fra1::n9c8v-1685884631577-4ed855e8d109
153
+ Connection:
154
+ - close
155
+ Transfer-Encoding:
156
+ - chunked
157
+ body:
158
+ encoding: ASCII-8BIT
159
+ string: 'Redirecting to /api/blogs/https:/rogue-scholar.org/api/posts/1jgo8yel
160
+ (308)
161
+
162
+ '
163
+ recorded_at: Sun, 04 Jun 2023 13:17:11 GMT
117
164
  recorded_with: VCR 6.1.0