commonmeta-ruby 3.3.17 → 3.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (44) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +37 -50
  3. data/bin/commonmeta +1 -1
  4. data/lib/commonmeta/cli.rb +7 -0
  5. data/lib/commonmeta/crossref_utils.rb +20 -0
  6. data/lib/commonmeta/readers/json_feed_reader.rb +19 -1
  7. data/lib/commonmeta/schema_utils.rb +1 -1
  8. data/lib/commonmeta/utils.rb +6 -4
  9. data/lib/commonmeta/version.rb +1 -1
  10. data/resources/{commonmeta_v0.9.2.json → commonmeta_v0.9.3.json} +32 -2
  11. data/spec/cli_spec.rb +1 -1
  12. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/blog_post_with_non-url_id.yml +84 -18
  13. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/blogger_post.yml +42 -14
  14. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_with_author_name_suffix.yml +184 -55
  15. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_with_doi.yml +76 -15
  16. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_with_institutional_author.yml +33 -12
  17. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_with_organizational_author.yml +44 -11
  18. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_with_related_identifiers.yml +366 -0
  19. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_without_doi.yml +144 -11
  20. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/jekyll_post.yml +42 -13
  21. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/jekyll_post_with_anonymous_author.yml +17 -13
  22. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/substack_post_with_broken_reference.yml +557 -262
  23. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/syldavia_gazette_post_with_references.yml +76 -47
  24. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/upstream_post_with_references.yml +303 -123
  25. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/wordpress_post.yml +108 -12
  26. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/wordpress_post_with_many_references.yml +3048 -441
  27. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/wordpress_post_with_references.yml +178 -31
  28. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/wordpress_post_with_tracking_code_on_url.yml +139 -17
  29. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/another_schema_org_from_front-matter.yml +47 -48
  30. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/journal_article.yml +5 -5
  31. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/journal_article_from_datacite.yml +7 -7
  32. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_feed_item_from_rogue_scholar_with_anonymous_author.yml +17 -13
  33. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_feed_item_from_rogue_scholar_with_doi.yml +108 -12
  34. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_feed_item_from_rogue_scholar_with_organizational_author.yml +44 -11
  35. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_feed_item_from_rogue_scholar_with_relations.yml +366 -0
  36. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_feed_item_from_upstream_blog.yml +200 -11
  37. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/json_feed_item_with_references.yml +303 -123
  38. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/posted_content.yml +16 -16
  39. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/schema_org_from_another_science_blog.yml +17 -17
  40. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/schema_org_from_front_matter.yml +111 -113
  41. data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/write_metadata_as_crossref/schema_org_from_upstream_blog.yml +64 -57
  42. data/spec/readers/json_feed_reader_spec.rb +85 -57
  43. data/spec/writers/crossref_xml_writer_spec.rb +76 -40
  44. metadata +6 -4
@@ -23,13 +23,13 @@ http_interactions:
23
23
  Cache-Control:
24
24
  - public, max-age=0, must-revalidate
25
25
  Content-Length:
26
- - '1680'
26
+ - '4529'
27
27
  Content-Type:
28
28
  - application/json; charset=utf-8
29
29
  Date:
30
- - Mon, 10 Jul 2023 21:04:47 GMT
30
+ - Wed, 06 Sep 2023 14:24:40 GMT
31
31
  Etag:
32
- - '"10p8jql4uqx1ai"'
32
+ - '"o1gypfhay03hb"'
33
33
  Server:
34
34
  - Vercel
35
35
  Strict-Transport-Security:
@@ -39,7 +39,7 @@ http_interactions:
39
39
  X-Vercel-Cache:
40
40
  - MISS
41
41
  X-Vercel-Id:
42
- - fra1::iad1::tkv5t-1689023087319-da88ab8eb283
42
+ - fra1::iad1::6rbj8-1694010279894-622b2a82ede7
43
43
  Connection:
44
44
  - close
45
45
  body:
@@ -47,14 +47,47 @@ http_interactions:
47
47
  string: '{"id":"5561f8e4-2ff1-4186-a8d5-8dacb3afe414","doi":"https://doi.org/10.59350/2shz7-ehx26","url":"https://libscie.org/ku-leuven-supports-researchequals","title":"KU
48
48
  Leuven supports ResearchEquals","summary":"KU Leuven is now an inaugural supporting
49
49
  member of ResearchEquals, sustaining and governing the development of modular
50
- publishing.As part of their commitment to Open Science, KU Leuven supports
50
+ publishing. As part of their commitment to Open Science, KU Leuven supports
51
51
  sustainable implementations of Open Access and Open Science through the KU
52
52
  Leuven Fund for Fair OA. The fund is usually only available to non-profits,
53
53
  but ResearchEquals’ governance convinced KU Leuven to support a for-profit
54
- initiative.“We don’t want to be too rigid in our approach...","published_at":1683614606,"updated_at":1683614606,"indexed_at":1689006804,"authors":[{"url":"https://ror.org/0342dzm54","name":"Liberate
55
- Science"}],"image":"https://libscie.org/content/images/2023/04/thank-you-1-.jpg","tags":["ResearchEquals"],"language":"en","reference":[],"blog_id":"h49ct36","blog_name":"Liberate
56
- Science","blog":{"id":"h49ct36","title":"Liberate Science","description":"Research
57
- as a commons","language":"en","favicon":"https://libscie.org/favicon.png","feed_url":"https://libscie.org/rss/","home_page_url":"https://libscie.org/","user_id":"8498eaf6-8c58-4b58-bc15-27eda292b1aa","created_at":"2023-05-31T14:08:03+00:00","indexed_at":"2023-01-04","feed_format":"application/rss+xml","license":"https://creativecommons.org/licenses/by/4.0/legalcode","generator":"Ghost
58
- 5.49","category":"Social Sciences","prefix":"10.59350","modified_at":"2023-07-04T06:30:20+00:00","version":"https://jsonfeed.org/version/1.1","backlog":true,"current_feed_url":null,"expired":null}}'
59
- recorded_at: Mon, 10 Jul 2023 21:04:47 GMT
54
+ initiative.","content_html":"<img src=\"https://libscie.org/content/images/2023/04/thank-you-1-.jpg\"
55
+ alt=\"KU Leuven supports ResearchEquals\" /><p>KU Leuven is now an inaugural
56
+ supporting member of ResearchEquals, sustaining and governing the development
57
+ of modular publishing.</p><p>As part of their commitment to Open Science,
58
+ KU Leuven supports sustainable implementations of Open Access and Open Science
59
+ through the <a href=\"https://www.kuleuven.be/open-science/what-is-open-science/scholarly-publishing-and-open-access/open-access-kuleuven/OS-services?ref=libscie.org\">KU
60
+ Leuven Fund for Fair OA</a>. The fund is usually only available to non-profits,
61
+ but ResearchEquals’ governance convinced KU Leuven to support a for-profit
62
+ initiative.</p><p>“We don’t want to be too rigid in our approach and understand
63
+ that publishing or other research infrastructures can work according to different
64
+ sustainability models. What matters to us is that, if profits are made, they
65
+ are reinvested in the academic community and that researchers remain firmly
66
+ in control.” Demmy Verbeke said.</p><p>Supporting members help sustain operations
67
+ and receive additional governance rights for <a href=\"https://researchequals.com/?ref=libscie.org\">ResearchEquals</a>.
68
+ These rights include the option to participate in quarterly assemblies, strategy
69
+ and decision making processes, the power to block acquisitions, and to request
70
+ more information around business operations. As a result, supporting members
71
+ shape how ResearchEquals evolves. Individuals can become supporting members
72
+ for 79.99 euro’s per year. Institutions can become supporting members for
73
+ a yearly contribution of at least 2500 euro’s. </p><p>ResearchEquals is an
74
+ open source, open access publishing platform for research modules. ResearchEquals
75
+ realized the first modular publishing platform (launched February 1st, 2022),
76
+ which revolves around sharing the research process, step by step, instead
77
+ of only the final report.</p><p>“It is great to see KU Leuven support generative
78
+ projects, regardless of whether they are for-profit or not” Chris Hartgerink
79
+ said.</p><p>KU Leuven is one of the first institutional supporting members
80
+ of ResearchEquals.</p><hr /><p>KU Leuven is one of the largest universities
81
+ in Belgium, with a strong commitment to open access and open science. Demmy
82
+ Verbeke and Laura Mesotten manage the Fund for Fair OA of KU Leuven Libraries.</p><p>Liberate
83
+ Science GmbH (est. 2019) cultivates alternative publishing formats that work
84
+ for researchers everywhere. ResearchEquals is a Liberate Science GmbH project.
85
+ For more information view the <a href=\"https://www.researchequals.com/supporting-member?ref=libscie.org\">supporting
86
+ member page</a> or contact CEO Chris Hartgerink (<a href=\"mailto:ceo@libscie.org\">ceo@libscie.org</a>).</p>","published_at":1683614606,"updated_at":1683614606,"indexed_at":1689006804,"authors":[{"url":"https://ror.org/0342dzm54","name":"Liberate
87
+ Science"}],"image":"https://libscie.org/content/images/2023/04/thank-you-1-.jpg","tags":["Research
88
+ Equals"],"language":"en","reference":[],"relationships":[],"blog_id":"h49ct36","blog_name":"Liberate
89
+ Science","blog_slug":"libscie","blog":{"id":"h49ct36","title":"Liberate Science","description":"Research
90
+ as a commons","language":"en","favicon":"https://libscie.org/favicon.png","feed_url":"https://libscie.org/rss/","home_page_url":"https://libscie.org","user_id":"dead81b3-8a8b-45c9-85fe-f01bb3948c77","created_at":"2023-01-04","feed_format":"application/rss+xml","license":"https://creativecommons.org/licenses/by/4.0/legalcode","generator":"Ghost
91
+ 5.49","category":"socialSciences","prefix":"10.59350","modified_at":"2023-08-29T07:00:56+00:00","version":"https://jsonfeed.org/version/1.1","current_feed_url":null,"status":"active","issn":null,"backlog":9999,"authors":null,"plan":"Starter","slug":"libscie","use_mastodon":false}}'
92
+ recorded_at: Wed, 06 Sep 2023 14:24:40 GMT
60
93
  recorded_with: VCR 6.2.0
@@ -0,0 +1,366 @@
1
+ ---
2
+ http_interactions:
3
+ - request:
4
+ method: get
5
+ uri: https://rogue-scholar.org/api/posts/8a4de443-3347-4b82-b57d-e3c82b6485fc
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
+ - '9265'
27
+ Content-Type:
28
+ - application/json; charset=utf-8
29
+ Date:
30
+ - Wed, 06 Sep 2023 14:27:19 GMT
31
+ Etag:
32
+ - '"1380dhtw0b375b"'
33
+ Server:
34
+ - Vercel
35
+ Strict-Transport-Security:
36
+ - max-age=63072000
37
+ X-Matched-Path:
38
+ - "/api/posts/[[...params]]"
39
+ X-Vercel-Cache:
40
+ - MISS
41
+ X-Vercel-Id:
42
+ - fra1::iad1::kdp9q-1694010438861-7c30b2b1e8ec
43
+ Connection:
44
+ - close
45
+ body:
46
+ encoding: UTF-8
47
+ string: '{"id":"8a4de443-3347-4b82-b57d-e3c82b6485fc","doi":"https://doi.org/10.53731/r79v4e1-97aq74v-ag578","url":"https://blog.front-matter.io/posts/differences-between-orcid-and-datacite-metadata","title":"Differences
48
+ between ORCID and DataCite Metadata","summary":"One of the first tasks for
49
+ DataCite in the European Commission-funded THOR project, which started in
50
+ June, was to contribute to a comparison of the ORCID and DataCite metadata
51
+ standards.","content_html":" <p><img src=\"https://blog.front-matter.io/content/images/2023/09/cat_and_dog-1.png\"
52
+ /></p><p>One of the first tasks for DataCite in the European Commission-funded
53
+ <a href=\"http://project-thor.eu/\">THOR project</a>, which started in June,
54
+ was to contribute to a comparison of the ORCID and DataCite metadata standards.
55
+ Together with ORCID, CERN, the British Library and Dryad we looked at how
56
+ contributors, organizations and artefacts - and the relations between them
57
+ - are described in the respective metadata schemata, and how they are implemented
58
+ in two example data repositories, <a href=\"http://archaeologydataservice.ac.uk/\">Archaeology
59
+ Data Service</a> and <a href=\"https://www.datadryad.org/\">Dryad Digital
60
+ Repository</a>.</p>\n<p>The focus of our work was on identifying major gaps.
61
+ Our report was finished and made publicly available last week (Fenner et al.,
62
+ <a href=\"https://blog.datacite.org/differences-between-orcid-and-datacite-metadata/#ref-https://doi.org/10.5281/ZENODO.30799\">2015</a>).
63
+ The key findings are summarized below:</p>\n<ul><li>Common Approach to Personal
64
+ Names</li><li>Standardized Contributor Roles</li><li>Standardized Relation
65
+ Types</li><li>Metadata for Organisations</li><li>Persistent Identifiers for
66
+ Projects</li><li>Harmonization of ORCID and DataCite Metadata</li></ul>\n<h3>Common
67
+ Approach to Personal Names</h3>\n<p>While a single input field for contributor
68
+ names is common, separate fields for given and family names are required for
69
+ <a href=\"http://docs.citationstyles.org/en/stable/specification.html#names\">proper
70
+ formatting of citations</a>. As long as citations to scholarly content rely
71
+ on properly formatted text rather than persistent identifiers, services holding
72
+ bibliographic information have to support these separate fields. Further work
73
+ is needed to help with the transition to separate input fields for given and
74
+ famliy names, and to handle contributors that are organizations or groups
75
+ of people.</p>\n<h3>Standardized Contributor Roles</h3>\n<p>The currently
76
+ existing vocabularies for <strong>contributor type</strong> (DataCite) and
77
+ <strong>contributor role</strong> (ORCID) provide a high-level description,
78
+ but fall short when trying to describe the author/creator contribution in
79
+ more detail. <a href=\"http://docs.casrai.org/CRediT\">Project CRediT</a>
80
+ is a multi-stakeholder initiative that has developed a common vocabulary with
81
+ 14 different contributor roles, and this vocabulary can be used to provide
82
+ this detail, e.g. who provided resources such as reagents or samples, who
83
+ did the statistical analysis, or who contributed to the methodology of a study.</p>\n<p>CRediT
84
+ is complementary to existing contributor role vocabularies such as those by
85
+ ORCID and DataCite. For contributor roles it is particularly important that
86
+ the same vocabulary is used across stakeholders, so that the roles described
87
+ in the data center can be forwarded first to DataCite, then to ORCID, and
88
+ then also to other places such as institutional repositories.</p>\n<h3>Standardized
89
+ Relation Types</h3>\n<p>Capturing relations between scholarly works such as
90
+ datasets in a standardized way is important, as these relations are used for
91
+ citations and thus the basis for many indicators of scholarly impact. Currently
92
+ used vocabularies for relation types between scholarly works, e.g. by CrossRef
93
+ and DataCite, only partly overlap. In addition we see differences in community
94
+ practices, e.g. some scholars but not others reserve the term citation for
95
+ links between two scholarly articles. The term data citation is sometimes
96
+ used for all links from scholarly works to datasets, but other times reserved
97
+ for formal citations appearing in reference lists.</p>\n<h3>Metadata for Organisations</h3>\n<p>Both
98
+ ORCID and DataCite not only provide persistent identifiers for people and
99
+ data, but they also collect metadata around these persistent identifiers,
100
+ in particular links to other identifiers. The use of persistent identifiers
101
+ for organizations lags behind the use of persistent identifiers for research
102
+ outputs and people, and more work is needed.</p>\n<h3>Persistent Identifiers
103
+ for Projects</h3>\n<p>Research projects are collaborative activities among
104
+ contributors that may change over time. Projects have a start and end date
105
+ and are often funded by a grant. The existing persistent identifier (PID)
106
+ infrastructure does support artefacts, contributors and organisations, but
107
+ there is no first-class PID support for projects. This creates a major gap
108
+ that becomes obvious when we try to describe the relationships between funders,
109
+ contributors and research outputs.</p>\n<p>Both the ORCID and DataCite metadata
110
+ support funding information, but only as direct links to contributors or research
111
+ outputs, respectively. This not only makes it difficult to exchange funding
112
+ information between DataCite and ORCID, but also fails to adequately model
113
+ the sometimes complex relationships, e.g. when multiple funders and grants
114
+ were involved in supporting a research output. We therefore not only need
115
+ persistent identifiers for projects, but also infrastructure for collecting
116
+ and aggregating links to contributors and artefacts.</p>\n<h3>Harmonization
117
+ of ORCID and DataCite Metadata</h3>\n<p>We identified significant differences
118
+ between the ORCID and DataCite metadata schema, and these differences hinder
119
+ the flow of information between the two services. Several different approaches
120
+ to overcome these differences are conceivable:</p>\n<ol><li>only use a common
121
+ subset, relying on linked persistent identifiers to get the full metadata</li><li>harmonize
122
+ the ORCID and DataCite metadata schemata</li><li>common API exchange formats
123
+ for metadata</li></ol>\n<p>The first approach is the linked open data approach,
124
+ and was designed specifically for scenarios like this. One limitation is that
125
+ it requires persistent identifiers for all relevant attributes (e.g. for every
126
+ creator/contributor in the DataCite metadata). One major objective for THOR
127
+ is therefore to increase the use of persistent identifiers, both by THOR partners,
128
+ and by the community at large.</p>\n<p>A common metadata schema between ORCID
129
+ and DataCite is neither feasible nor necessarily needed. In addition, we have
130
+ to also consider interoperability with other metadata standards (e.g. CASRAI,
131
+ OpenAIRE, COAR), and with other artifacts, such as those having CrossRef DOIs.
132
+ What is more realistic is harmonization across a limited set essential metadata.</p>\n<p>The
133
+ third approach to improve interoperability uses a common API format that includes
134
+ all the metadata that need to be exchanged, but doesn’t require the metadata
135
+ schema itself to change. This approach was <a href=\"https://www.crossref.org/blog/crossref-and-datacite-unify-support-for-http-content-negotiation/\">taken
136
+ by DataCite and CrossRef a few years ago</a> to provide metadata for DOIs
137
+ in a consistent way despite significant differences in the CrossRef and DataCite
138
+ metadata schema. Using HTTP content negotiation, metadata are provided in
139
+ a variety of formats.</p>\n<h2>References</h2>\n<p>Fenner M, Demeranville
140
+ T, Kotarski R, et al. <em>D2.1: Artefact, Contributor, And Organisation Relationship
141
+ Data Schema</em>. Zenodo; 2015. doi:<a href=\"https://doi.org/10.5281/ZENODO.30799\">10.5281/ZENODO.30799</a></p>\n<h2>Notes</h2>\n<p>This
142
+ blog post was <a href=\"https://doi.org/10.5438/bc11-cqw1\">originally published</a>
143
+ on the DataCite Blog.</p> ","published_at":1442534400,"updated_at":1693949721,"indexed_at":1693950834,"authors":[{"url":"https://orcid.org/0000-0003-1419-2405","name":"Martin
144
+ Fenner"}],"image":"https://blog.front-matter.io/content/images/2023/09/cat_and_dog-1.png","tags":["Feature"],"language":"en","reference":[{"doi":"https://doi.org/10.5281/ZENODO.30799","key":"ref1"}],"relationships":[{"url":"https://doi.org/10.5438/bc11-cqw1","type":"IsIdenticalTo"}],"blog_id":"f0m0e38","blog_name":"Front
145
+ Matter","blog_slug":"front_matter","blog":{"id":"f0m0e38","title":"Front Matter","description":"The
146
+ Front Matter Blog covers the intersection of science and technology since
147
+ 2007.","language":"en","favicon":"https://blog.front-matter.io/favicon.png","feed_url":"https://blog.front-matter.io/atom-complete/","home_page_url":"https://blog.front-matter.io","user_id":"8498eaf6-8c58-4b58-bc15-27eda292b1aa","created_at":"2023-01-02","feed_format":"application/atom+xml","license":"https://creativecommons.org/licenses/by/4.0/legalcode","generator":"Ghost
148
+ 5.52","category":"computerAndInformationSciences","prefix":"10.53731","modified_at":"2023-09-05T21:35:21+00:00","version":"https://jsonfeed.org/version/1.1","current_feed_url":"https://blog.front-matter.io/atom/","status":"active","issn":"2749-9952","backlog":0,"authors":null,"plan":"Team","slug":"front_matter","use_mastodon":true}}'
149
+ recorded_at: Wed, 06 Sep 2023 14:27:19 GMT
150
+ - request:
151
+ method: get
152
+ uri: https://doi.org/10.5281/ZENODO.30799
153
+ body:
154
+ encoding: UTF-8
155
+ string: ''
156
+ headers:
157
+ Accept:
158
+ - application/vnd.citationstyles.csl+json
159
+ Connection:
160
+ - close
161
+ Host:
162
+ - doi.org
163
+ User-Agent:
164
+ - http.rb/5.1.1
165
+ response:
166
+ status:
167
+ code: 302
168
+ message: Found
169
+ headers:
170
+ Date:
171
+ - Wed, 06 Sep 2023 14:27:19 GMT
172
+ Content-Type:
173
+ - text/html;charset=utf-8
174
+ Content-Length:
175
+ - '183'
176
+ Connection:
177
+ - close
178
+ Location:
179
+ - https://data.crosscite.org/10.5281%2FZENODO.30799
180
+ Vary:
181
+ - Accept
182
+ Expires:
183
+ - Wed, 06 Sep 2023 15:22:17 GMT
184
+ Permissions-Policy:
185
+ - interest-cohort=(),browsing-topics=()
186
+ Cf-Cache-Status:
187
+ - DYNAMIC
188
+ Report-To:
189
+ - '{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=HfJ%2FINqIlNf1clkRNyNk1w4kyj2tWeLv%2Fk%2Bq1TPJfiWesgUC5k0QZJKvdec6chW%2BuxaeEQ8k1ha4KbZHFSOoWJ5MaWcPBNTbY0P3dcIeKDW6Jngg%2Bmm2V%2Bs%3D"}],"group":"cf-nel","max_age":604800}'
190
+ Nel:
191
+ - '{"success_fraction":0,"report_to":"cf-nel","max_age":604800}'
192
+ Strict-Transport-Security:
193
+ - max-age=31536000; includeSubDomains; preload
194
+ Server:
195
+ - cloudflare
196
+ Cf-Ray:
197
+ - 80276460fd026907-FRA
198
+ Alt-Svc:
199
+ - h3=":443"; ma=86400
200
+ body:
201
+ encoding: UTF-8
202
+ string: |-
203
+ <html><head><title>Handle Redirect</title></head>
204
+ <body><a href="https://data.crosscite.org/10.5281%2FZENODO.30799">https://data.crosscite.org/10.5281%2FZENODO.30799</a></body></html>
205
+ recorded_at: Wed, 06 Sep 2023 14:27:19 GMT
206
+ - request:
207
+ method: get
208
+ uri: https://data.crosscite.org/10.5281%2FZENODO.30799
209
+ body:
210
+ encoding: UTF-8
211
+ string: ''
212
+ headers:
213
+ Accept:
214
+ - application/vnd.citationstyles.csl+json
215
+ Connection:
216
+ - close
217
+ User-Agent:
218
+ - http.rb/5.1.1
219
+ Host:
220
+ - data.crosscite.org
221
+ response:
222
+ status:
223
+ code: 200
224
+ message: OK
225
+ headers:
226
+ Date:
227
+ - Wed, 06 Sep 2023 14:27:21 GMT
228
+ Content-Type:
229
+ - application/vnd.citationstyles.csl+json; charset=utf-8
230
+ Transfer-Encoding:
231
+ - chunked
232
+ Connection:
233
+ - close
234
+ Status:
235
+ - 200 OK
236
+ Cache-Control:
237
+ - max-age=0, private, must-revalidate
238
+ Vary:
239
+ - Accept-Encoding, Origin
240
+ Etag:
241
+ - W/"808492baef8e3e4af0fa6812bc25a08c"
242
+ X-Runtime:
243
+ - '0.018245'
244
+ X-Request-Id:
245
+ - d5ae8229-4153-405b-9f97-9473171213d7
246
+ X-Powered-By:
247
+ - Phusion Passenger(R) 6.0.13
248
+ Server:
249
+ - nginx/1.18.0 + Phusion Passenger(R) 6.0.13
250
+ body:
251
+ encoding: UTF-8
252
+ string: |-
253
+ {
254
+ "type": "report",
255
+ "id": "https://doi.org/10.5281/zenodo.30799",
256
+ "categories": [
257
+ "persistent identifier",
258
+ "pid",
259
+ "orcid",
260
+ "doi",
261
+ "datacite"
262
+ ],
263
+ "author": [
264
+ {
265
+ "family": "Fenner",
266
+ "given": "Martin"
267
+ },
268
+ {
269
+ "family": "Demeranville",
270
+ "given": "Tom"
271
+ },
272
+ {
273
+ "family": "Kotarski",
274
+ "given": "Rachael"
275
+ },
276
+ {
277
+ "family": "Vision",
278
+ "given": "Todd"
279
+ },
280
+ {
281
+ "family": "Rueda",
282
+ "given": "Laura"
283
+ },
284
+ {
285
+ "family": "Dasler",
286
+ "given": "Robin"
287
+ },
288
+ {
289
+ "family": "Haak",
290
+ "given": "Laure"
291
+ },
292
+ {
293
+ "family": "Cruse",
294
+ "given": "Patricia"
295
+ }
296
+ ],
297
+ "issued": {
298
+ "date-parts": [
299
+ [
300
+ 2015,
301
+ 9,
302
+ 11
303
+ ]
304
+ ]
305
+ },
306
+ "abstract": "This document identifies gaps in existing PID infrastructures, with a focus on ORCID and DataCite Metadata and links between contributors, organizations and artefacts. What prevents us from establishing interoperability and overcoming barriers between PID platforms for contributors, artefacts and organisations, and research solutions for federated attribution, claiming, publishing and direct data access? It goes on to propose strategies to overcome these gaps.",
307
+ "DOI": "10.5281/ZENODO.30799",
308
+ "publisher": "Zenodo",
309
+ "title": "D2.1: Artefact, Contributor, And Organisation Relationship Data Schema",
310
+ "URL": "https://zenodo.org/record/30799",
311
+ "copyright": "Creative Commons Attribution 4.0"
312
+ }
313
+ recorded_at: Wed, 06 Sep 2023 14:27:21 GMT
314
+ - request:
315
+ method: head
316
+ uri: https://doi.org/10.5438/bc11-cqw1
317
+ body:
318
+ encoding: UTF-8
319
+ string: ''
320
+ headers:
321
+ Connection:
322
+ - close
323
+ Host:
324
+ - doi.org
325
+ User-Agent:
326
+ - http.rb/5.1.1
327
+ response:
328
+ status:
329
+ code: 302
330
+ message: Found
331
+ headers:
332
+ Date:
333
+ - Wed, 06 Sep 2023 14:27:21 GMT
334
+ Content-Type:
335
+ - text/html;charset=utf-8
336
+ Content-Length:
337
+ - '233'
338
+ Connection:
339
+ - close
340
+ Location:
341
+ - https://datacite.org/blog/differences-between-orcid-and-datacite-metadata/
342
+ Vary:
343
+ - Accept
344
+ Expires:
345
+ - Wed, 06 Sep 2023 14:34:12 GMT
346
+ Permissions-Policy:
347
+ - interest-cohort=(),browsing-topics=()
348
+ Cf-Cache-Status:
349
+ - DYNAMIC
350
+ Report-To:
351
+ - '{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=WlCur2YM%2BnSuhBmd%2BuAH%2BXnUzDOrP1HOBpYF%2F62pmS9GkIuLLkbrvgyL98NNnuKEjcjkjgP9qrwQCNM0x6%2FgmMkSI4uUT3fScDcp0lyCAJiy89on5cvGk3U%3D"}],"group":"cf-nel","max_age":604800}'
352
+ Nel:
353
+ - '{"success_fraction":0,"report_to":"cf-nel","max_age":604800}'
354
+ Strict-Transport-Security:
355
+ - max-age=31536000; includeSubDomains; preload
356
+ Server:
357
+ - cloudflare
358
+ Cf-Ray:
359
+ - 8027646d0cba9176-FRA
360
+ Alt-Svc:
361
+ - h3=":443"; ma=86400
362
+ body:
363
+ encoding: UTF-8
364
+ string: ''
365
+ recorded_at: Wed, 06 Sep 2023 14:27:21 GMT
366
+ recorded_with: VCR 6.2.0
@@ -23,13 +23,13 @@ http_interactions:
23
23
  Cache-Control:
24
24
  - public, max-age=0, must-revalidate
25
25
  Content-Length:
26
- - '1654'
26
+ - '13845'
27
27
  Content-Type:
28
28
  - application/json; charset=utf-8
29
29
  Date:
30
- - Mon, 10 Jul 2023 21:04:52 GMT
30
+ - Wed, 06 Sep 2023 14:27:16 GMT
31
31
  Etag:
32
- - '"pkkw16ms8919y"'
32
+ - '"9vk0oiu0agaob"'
33
33
  Server:
34
34
  - Vercel
35
35
  Strict-Transport-Security:
@@ -39,7 +39,7 @@ http_interactions:
39
39
  X-Vercel-Cache:
40
40
  - MISS
41
41
  X-Vercel-Id:
42
- - fra1::iad1::q9hc8-1689023092238-8f72026f2bf3
42
+ - fra1::iad1::2nsgw-1694010435634-7ef529f76f47
43
43
  Connection:
44
44
  - close
45
45
  body:
@@ -47,13 +47,146 @@ http_interactions:
47
47
  string: '{"id":"c3095752-2af0-40a4-a229-3ceb7424bce2","doi":"https://doi.org/10.59350/kj95y-gp867","url":"https://www.ideasurg.pub/residency-visual-abstract","title":"The
48
48
  Residency Visual Abstract","summary":"My prototype for a Residency Visual
49
49
  AbstractThis tool represents my own ideas and is not currently in use or endorsed
50
- by any institution.Medical students applying to residency often have to grapple
50
+ by any institution. Medical students applying to residency often have to grapple
51
51
  with an incredible amount of information when evaluating prospective training
52
52
  programs. The increased number of applications and interviews inherent to
53
- the Zoom era further exacerbates this issue. At the same time, programs need
54
- to find ways to communicate a great deal of information to applicants....","published_at":1680982354,"updated_at":1680982354,"indexed_at":1688982864,"authors":[{"url":null,"name":"Tejas
55
- S. Sathe, MD"}],"image":null,"tags":[],"language":"en","reference":[],"blog_id":"3cxcm20","blog_name":"I.D.E.A.S.","blog":{"id":"3cxcm20","title":"I.D.E.A.S.","description":"Innovation
56
- and Design Experiments in Academic Surgery (I.D.E.A.S.)","language":"en","favicon":"https://www.ideasurg.pub/favicon.png","feed_url":"https://www.ideasurg.pub/rss/","home_page_url":"https://www.ideasurg.pub/","user_id":"8498eaf6-8c58-4b58-bc15-27eda292b1aa","created_at":"2023-05-31T13:44:29+00:00","indexed_at":"2023-01-04","feed_format":"application/rss+xml","license":"https://creativecommons.org/licenses/by/4.0/legalcode","generator":"Ghost
57
- 5.53","category":"Medical and Health Sciences","prefix":"10.59350","modified_at":"2023-06-03T04:54:30+00:00","version":"https://jsonfeed.org/version/1.1","backlog":false,"current_feed_url":null,"expired":null}}'
58
- recorded_at: Mon, 10 Jul 2023 21:04:52 GMT
53
+ the Zoom era further exacerbates this issue.","content_html":"<figure><img
54
+ src=\"https://www.ideasurg.pub/content/images/2023/04/Residency-Scorecard-Light-Mode--7-.png\"
55
+ loading=\"lazy\" width=\"2000\" height=\"1127\" srcset=\"https://www.ideasurg.pub/content/images/size/w600/2023/04/Residency-Scorecard-Light-Mode--7-.png
56
+ 600w, https://www.ideasurg.pub/content/images/size/w1000/2023/04/Residency-Scorecard-Light-Mode--7-.png
57
+ 1000w, https://www.ideasurg.pub/content/images/size/w1600/2023/04/Residency-Scorecard-Light-Mode--7-.png
58
+ 1600w, https://www.ideasurg.pub/content/images/size/w2400/2023/04/Residency-Scorecard-Light-Mode--7-.png
59
+ 2400w\" /><figcaption>My prototype for a Residency Visual Abstract</figcaption></figure><div><div>This
60
+ tool represents my own ideas and is not currently in use or endorsed by any
61
+ institution.</div></div><p>Medical students applying to residency often have
62
+ to grapple with an incredible amount of information when evaluating prospective
63
+ training programs. The increased number of applications and interviews inherent
64
+ to the Zoom era further exacerbates this issue. At the same time, programs
65
+ need to find ways to communicate a great deal of information to applicants.
66
+ Due to the proliferation of social media, this communication is both more
67
+ extensive and more longitudinal than a one hour presentation on interview
68
+ day.</p><p>The traditional interview day presentation is a slide presentation
69
+ that provides several factual details about a program. While each program
70
+ is slightly different, most of these presentations cover common ground - including
71
+ where residents rotate, what services they do, where alumni match into fellowship,
72
+ examination pass rates, and information on professional development and research
73
+ activities. These presentations can often be long (I once helped edit a slide
74
+ deck that had 60 slides in it!) and difficult to recall. Furthermore, updating
75
+ these slides from year to year is a time consuming challenge. Finally, most
76
+ of these presentations are done in a traditional bullet point format with
77
+ few slides reserved for photos. Few are designed in a way that optimizes user
78
+ experience.</p><p>In my opinion, the most important quality of the program
79
+ is how well a prospective applicant fits in with the resident culture. Though
80
+ it is impossible to put into numbers, it has an outsized impact on a resident''s
81
+ experience and wellness. Furthermore, it is even harder to intuit in the absence
82
+ of an in-person interview experience. Nevertheless, there are important quantitative
83
+ metrics that applicants consider and programs want to showcase. However, there
84
+ is not yet a standardized, accessible, and visually appealing format to do
85
+ so. Given the challenges in communicating these details as well as the growing
86
+ power of social media , I wanted to design a new way that programs can effectively
87
+ and efficiently display and disseminate this information so that applicants
88
+ can be more informed and programs can better utilize their interview days
89
+ to convey the critical intangibles.</p><p>In the distinct but not quite distant
90
+ field of surgical research, the visual abstract has already proven to be an
91
+ excellent means of distilling a research study filled with details into an
92
+ easy-to-digest and visually pleasing format. Developed by Dr. Andrew Ibrahim
93
+ and colleagues, the visual abstract has already been adopted by 50 journals,
94
+ and a study by the creators <a href=\"https://journals.lww.com/annalsofsurgery/Citation/2017/12000/Visual_Abstracts_to_Disseminate_Research_on_Social.36.aspx?ref=ideasurg.pub\">demonstrated</a>
95
+ that the presence of a visual abstract can more than double article visits
96
+ and increase impressions more than seven-fold. An excellent primer discussing
97
+ how to develop a visual abstract and highlighting its use in academic journals
98
+ is available <a href=\"https://static1.squarespace.com/static/5854aaa044024321a353bb0d/t/5a527aa89140b76bbfb2028a/1515354827682/VisualAbstract_Primer_v4_1.pdf?ref=ideasurg.pub\">here</a>.
99
+ </p><p>A variant of the visual abstract has also been used by residency programs
100
+ on social media in the past. An example from the Duke Surgery Residency program
101
+ is shown here:</p><figure><blockquote><p>We’re so excited to meet <a href=\"https://twitter.com/hashtag/GenSurgMatch2023?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#GenSurgMatch2023</a>
102
+ applicants over the next few months! Check out our latest <a href=\"https://twitter.com/DukeSurgRes?ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">@DukeSurgRes</a>
103
+ <a href=\"https://twitter.com/hashtag/VisualAbstract?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#VisualAbstract</a>
104
+ <a href=\"https://twitter.com/hashtag/ByTheNumbers?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#ByTheNumbers</a>.
105
+ We hope you can visualize your <a href=\"https://twitter.com/hashtag/SutureFuture?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#SutureFuture</a>
106
+ at <a href=\"https://twitter.com/DukeSurgery?ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">@DukeSurgery</a>.
107
+ <a href=\"https://twitter.com/hashtag/SabistonSquad?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#SabistonSquad</a>
108
+ <a href=\"https://twitter.com/hashtag/SurgTwitter?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#SurgTwitter</a>
109
+ <a href=\"https://twitter.com/hashtag/MedTwitter?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#MedTwitter</a>
110
+ <a href=\"https://twitter.com/hashtag/SurgEd?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#SurgEd</a>
111
+ <a href=\"https://twitter.com/hashtag/ILookLikeASurgeon?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#ILookLikeASurgeon</a>
112
+ <a href=\"https://t.co/6ZqnfFrWE5?ref=ideasurg.pub\">pic.twitter.com/6ZqnfFrWE5</a></p>—
113
+ Duke General Surgery Residency (@DukeSurgRes) <a href=\"https://twitter.com/DukeSurgRes/status/1587460003941810179?ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">November
114
+ 1, 2022</a></blockquote>\n\n</figure><p>Inspired by this format, I tried to
115
+ design a version tailored towards prospective surgery trainees. I wanted to
116
+ see if I could boil down the complexity of a program into the fewest pieces
117
+ of data possible and present them in a user-friendly interface. </p><h3>The
118
+ Visual Abstract</h3><p>The abstract contains six different categories: demographics,
119
+ operative volume, education, research, fellowships, and other. The goal is
120
+ to capture relevant information regarding the tripartite mission of academic
121
+ surgery as well as understand a program''s strengths in diversity and inclusion
122
+ and career preparation. For each category, discrete data points were chosen
123
+ which can easily allow applicants to contextualize a program''s strengths
124
+ and weaknesses. The other category contains a checklist of features that applicants
125
+ seem to care about (based on observations and conversations though certainly
126
+ not proven scientifically). Finally, there is a space for QR codes to link
127
+ to the program website as well as a copy of the contract that matched applicants
128
+ will need to sign (as <a href=\"https://www.nrmp.org/wp-content/uploads/2022/09/2023-MPA-Main-Match-Program-FINAL-3.pdf?ref=ideasurg.pub\">required</a>
129
+ by the National Resident Matching Program).</p><p>Of course, the tool comes
130
+ with a dark mode!</p><figure><img src=\"https://www.ideasurg.pub/content/images/2023/04/Thumbnail--2-.png\"
131
+ loading=\"lazy\" width=\"1924\" height=\"1084\" srcset=\"https://www.ideasurg.pub/content/images/size/w600/2023/04/Thumbnail--2-.png
132
+ 600w, https://www.ideasurg.pub/content/images/size/w1000/2023/04/Thumbnail--2-.png
133
+ 1000w, https://www.ideasurg.pub/content/images/size/w1600/2023/04/Thumbnail--2-.png
134
+ 1600w, https://www.ideasurg.pub/content/images/2023/04/Thumbnail--2-.png 1924w\"
135
+ /></figure><h3>What this is</h3><p>This visual abstract can provide a semi-standardized
136
+ format for programs to share important information with applicants allowing
137
+ them to compare important metrics in a comprehensive, “easy” way. It is important
138
+ to note that each of these data points is meant to be an objective measure
139
+ without any comment on its intrinsic value. For example, one program may have
140
+ a significantly higher case volume than peer institutions but less protected
141
+ education time. Another may have a robotic curriculum but not have any recent
142
+ chiefs who matched into Pediatric Surgery. None of these are independently
143
+ good or bad, but applicants should have an easy way to understand the factors
144
+ so that they can make the most informed decision. If a significant number
145
+ of programs adopt the visual abstract, it will naturally create incentives
146
+ for programs to share and improve on these metrics with transparency. In this
147
+ manner, healthy competition can actually generate an incentive to improve
148
+ program offerings for current residents as well (though this can have unintended
149
+ consequences…see limitations).</p><p>Some may question the wisdom of putting
150
+ these numbers out in the open - especially if they are not where a program
151
+ wants them to be. However, some of the information is publicly <a href=\"https://www.absurgery.org/xfer/3yr_summary.pdf?ref=ideasurg.pub\">available</a>.
152
+ Many of these data points are already reported on during the interview process.
153
+ Moreover, most applicants want to know this information and value transparency.
154
+ Ultimately, no program is perfect, and how a program chooses to address perceived
155
+ strengths and weaknesses reflects its core values.</p><h3>What this is not
156
+ and other limitations</h3><p>No visual abstract, slide deck, or document will
157
+ be able to capture the full picture of a residency program - which at its
158
+ core is a collection of human beings. It is worth repeating that the most
159
+ important consideration students should make when choosing a program is missing
160
+ from this work. Furthermore, the exact data points used may not be correct.
161
+ At one point, I considered putting a box for ABSITE pass rate, however I thought
162
+ this was antithetical to the ABSITE''s stated aim of being a <a href=\"https://www.absurgery.org/default.jsp?certabsite=&amp;ref=ideasurg.pub\">formative</a>,
163
+ not a summative, assessment. Furthermore, there is no box specifying the number
164
+ of LGBTQ residents in a program. While this is an essential component of diversity,
165
+ equity, and inclusion, it was omitted due to the fact that some of these residents
166
+ may not be publicly out and this would lead to an inaccurate representation.
167
+ Another missing box is the number of residents with children, given that family
168
+ support is an increasingly recognized feature that students are looking for
169
+ in training programs.</p><p>I would like for this to be even less cluttered
170
+ - and user feedback can drive further reduction of content such that the distilled
171
+ final version is even more elegant. Currently, the vision for this project
172
+ is that of a grassroots project, where individual programs can choose to use,
173
+ improve, and modify this template to broadcast important information to applicants.
174
+ However, I am wary of the general principle that once quantitative metrics
175
+ are used by a central authority to rank, there is a natural tendency to gamify
176
+ those metrics whether or not the underlying feature they seek to estimate
177
+ is actually affected.</p><h3>What to do with this template</h3><p>In short,
178
+ whatever you would like. The template was built in Figma, which has become
179
+ the industry-standard in visual design. It is free to make a basic Figma account,
180
+ and the full suite of features is also available for free with proof of affiliation
181
+ with a university. Figma offers the ability to comment on a template as well
182
+ as duplicate or \"remix\" the template for personal use. I would appreciate
183
+ your feedback on how to make this template better. Moreover, I encourage you
184
+ to take it, modify it, improve it, and share your changes publicly. Together,
185
+ we can continue to iteratively design this initial prototype and develop a
186
+ robust, user-friendly tool that provides values to students, residents, and
187
+ programs alike.</p><h3>Comment, remix, make it your own!</h3><p><a href=\"https://www.figma.com/community/file/1226056013352001653?ref=ideasurg.pub\">https://www.figma.com/community/file/1226056013352001653</a></p>","published_at":1680982354,"updated_at":1680982354,"indexed_at":1690924548,"authors":[{"url":"https://orcid.org/0000-0003-0449-4469","name":"Tejas
188
+ S. Sathe"}],"image":"https://www.ideasurg.pub/content/images/2023/04/Residency-Scorecard-Light-Mode--7-.png","tags":[],"language":"en","reference":[],"relationships":[],"blog_id":"3cxcm20","blog_name":"I.D.E.A.S.","blog_slug":"ideas","blog":{"id":"3cxcm20","title":"I.D.E.A.S.","description":"Innovation
189
+ and Design Experiments in Academic Surgery (I.D.E.A.S.)","language":"en","favicon":"https://www.ideasurg.pub/favicon.png","feed_url":"https://www.ideasurg.pub/rss/","home_page_url":"https://www.ideasurg.pub","user_id":"4cecb4b8-58b5-49fe-9edb-6af638294ef5","created_at":"2023-01-04","feed_format":"application/rss+xml","license":"https://creativecommons.org/licenses/by/4.0/legalcode","generator":"Ghost
190
+ 5.61","category":"clinicalMedicine","prefix":"10.59350","modified_at":"2023-07-29T22:28:28+00:00","version":"https://jsonfeed.org/version/1.1","current_feed_url":null,"status":"active","issn":"2993-1150","backlog":0,"authors":null,"plan":"Starter","slug":"ideas","use_mastodon":false}}'
191
+ recorded_at: Wed, 06 Sep 2023 14:27:16 GMT
59
192
  recorded_with: VCR 6.2.0