commonmeta-ruby 3.3.18 → 3.4.1

data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_with_related_identifiers.yml

@@ -0,0 +1,366 @@
+---
+http_interactions:
+- request:
+    method: get
+    uri: https://rogue-scholar.org/api/posts/8a4de443-3347-4b82-b57d-e3c82b6485fc
+    body:
+      encoding: UTF-8
+      string: ''
+    headers:
+      Connection:
+      - close
+      Host:
+      - rogue-scholar.org
+      User-Agent:
+      - http.rb/5.1.1
+  response:
+    status:
+      code: 200
+      message: OK
+    headers:
+      Age:
+      - '0'
+      Cache-Control:
+      - public, max-age=0, must-revalidate
+      Content-Length:
+      - '9265'
+      Content-Type:
+      - application/json; charset=utf-8
+      Date:
+      - Wed, 06 Sep 2023 14:27:19 GMT
+      Etag:
+      - '"1380dhtw0b375b"'
+      Server:
+      - Vercel
+      Strict-Transport-Security:
+      - max-age=63072000
+      X-Matched-Path:
+      - "/api/posts/[[...params]]"
+      X-Vercel-Cache:
+      - MISS
+      X-Vercel-Id:
+      - fra1::iad1::kdp9q-1694010438861-7c30b2b1e8ec
+      Connection:
+      - close
+    body:
+      encoding: UTF-8
+      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
+        between ORCID and DataCite Metadata","summary":"One of the first tasks for
+        DataCite in the European Commission-funded THOR project, which started in
+        June, was to contribute to a comparison of the ORCID and DataCite metadata
+        standards.","content_html":" <p><img src=\"https://blog.front-matter.io/content/images/2023/09/cat_and_dog-1.png\"
+        /></p><p>One of the first tasks for DataCite in the European Commission-funded
+        <a href=\"http://project-thor.eu/\">THOR project</a>, which started in June,
+        was to contribute to a comparison of the ORCID and DataCite metadata standards.
+        Together with ORCID, CERN, the British Library and Dryad we looked at how
+        contributors, organizations and artefacts - and the relations between them
+        - are described in the respective metadata schemata, and how they are implemented
+        in two example data repositories, <a href=\"http://archaeologydataservice.ac.uk/\">Archaeology
+        Data Service</a> and <a href=\"https://www.datadryad.org/\">Dryad Digital
+        Repository</a>.</p>\n<p>The focus of our work was on identifying major gaps.
+        Our report was finished and made publicly available last week (Fenner et al.,
+        <a href=\"https://blog.datacite.org/differences-between-orcid-and-datacite-metadata/#ref-https://doi.org/10.5281/ZENODO.30799\">2015</a>).
+        The key findings are summarized below:</p>\n<ul><li>Common Approach to Personal
+        Names</li><li>Standardized Contributor Roles</li><li>Standardized Relation
+        Types</li><li>Metadata for Organisations</li><li>Persistent Identifiers for
+        Projects</li><li>Harmonization of ORCID and DataCite Metadata</li></ul>\n<h3>Common
+        Approach to Personal Names</h3>\n<p>While a single input field for contributor
+        names is common, separate fields for given and family names are required for
+        <a href=\"http://docs.citationstyles.org/en/stable/specification.html#names\">proper
+        formatting of citations</a>. As long as citations to scholarly content rely
+        on properly formatted text rather than persistent identifiers, services holding
+        bibliographic information have to support these separate fields. Further work
+        is needed to help with the transition to separate input fields for given and
+        famliy names, and to handle contributors that are organizations or groups
+        of people.</p>\n<h3>Standardized Contributor Roles</h3>\n<p>The currently
+        existing vocabularies for <strong>contributor type</strong> (DataCite) and
+        <strong>contributor role</strong> (ORCID) provide a high-level description,
+        but fall short when trying to describe the author/creator contribution in
+        more detail. <a href=\"http://docs.casrai.org/CRediT\">Project CRediT</a>
+        is a multi-stakeholder initiative that has developed a common vocabulary with
+        14 different contributor roles, and this vocabulary can be used to provide
+        this detail, e.g. who provided resources such as reagents or samples, who
+        did the statistical analysis, or who contributed to the methodology of a study.</p>\n<p>CRediT
+        is complementary to existing contributor role vocabularies such as those by
+        ORCID and DataCite. For contributor roles it is particularly important that
+        the same vocabulary is used across stakeholders, so that the roles described
+        in the data center can be forwarded first to DataCite, then to ORCID, and
+        then also to other places such as institutional repositories.</p>\n<h3>Standardized
+        Relation Types</h3>\n<p>Capturing relations between scholarly works such as
+        datasets in a standardized way is important, as these relations are used for
+        citations and thus the basis for many indicators of scholarly impact. Currently
+        used vocabularies for relation types between scholarly works, e.g. by CrossRef
+        and DataCite, only partly overlap. In addition we see differences in community
+        practices, e.g. some scholars but not others reserve the term citation for
+        links between two scholarly articles. The term data citation is sometimes
+        used for all links from scholarly works to datasets, but other times reserved
+        for formal citations appearing in reference lists.</p>\n<h3>Metadata for Organisations</h3>\n<p>Both
+        ORCID and DataCite not only provide persistent identifiers for people and
+        data, but they also collect metadata around these persistent identifiers,
+        in particular links to other identifiers. The use of persistent identifiers
+        for organizations lags behind the use of persistent identifiers for research
+        outputs and people, and more work is needed.</p>\n<h3>Persistent Identifiers
+        for Projects</h3>\n<p>Research projects are collaborative activities among
+        contributors that may change over time. Projects have a start and end date
+        and are often funded by a grant. The existing persistent identifier (PID)
+        infrastructure does support artefacts, contributors and organisations, but
+        there is no first-class PID support for projects. This creates a major gap
+        that becomes obvious when we try to describe the relationships between funders,
+        contributors and research outputs.</p>\n<p>Both the ORCID and DataCite metadata
+        support funding information, but only as direct links to contributors or research
+        outputs, respectively. This not only makes it difficult to exchange funding
+        information between DataCite and ORCID, but also fails to adequately model
+        the sometimes complex relationships, e.g. when multiple funders and grants
+        were involved in supporting a research output. We therefore not only need
+        persistent identifiers for projects, but also infrastructure for collecting
+        and aggregating links to contributors and artefacts.</p>\n<h3>Harmonization
+        of ORCID and DataCite Metadata</h3>\n<p>We identified significant differences
+        between the ORCID and DataCite metadata schema, and these differences hinder
+        the flow of information between the two services. Several different approaches
+        to overcome these differences are conceivable:</p>\n<ol><li>only use a common
+        subset, relying on linked persistent identifiers to get the full metadata</li><li>harmonize
+        the ORCID and DataCite metadata schemata</li><li>common API exchange formats
+        for metadata</li></ol>\n<p>The first approach is the linked open data approach,
+        and was designed specifically for scenarios like this. One limitation is that
+        it requires persistent identifiers for all relevant attributes (e.g. for every
+        creator/contributor in the DataCite metadata). One major objective for THOR
+        is therefore to increase the use of persistent identifiers, both by THOR partners,
+        and by the community at large.</p>\n<p>A common metadata schema between ORCID
+        and DataCite is neither feasible nor necessarily needed. In addition, we have
+        to also consider interoperability with other metadata standards (e.g. CASRAI,
+        OpenAIRE, COAR), and with other artifacts, such as those having CrossRef DOIs.
+        What is more realistic is harmonization across a limited set essential metadata.</p>\n<p>The
+        third approach to improve interoperability uses a common API format that includes
+        all the metadata that need to be exchanged, but doesn’t require the metadata
+        schema itself to change. This approach was <a href=\"https://www.crossref.org/blog/crossref-and-datacite-unify-support-for-http-content-negotiation/\">taken
+        by DataCite and CrossRef a few years ago</a> to provide metadata for DOIs
+        in a consistent way despite significant differences in the CrossRef and DataCite
+        metadata schema. Using HTTP content negotiation, metadata are provided in
+        a variety of formats.</p>\n<h2>References</h2>\n<p>Fenner M, Demeranville
+        T, Kotarski R, et al. <em>D2.1: Artefact, Contributor, And Organisation Relationship
+        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
+        blog post was <a href=\"https://doi.org/10.5438/bc11-cqw1\">originally published</a>
+        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
+        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
+        Matter","blog_slug":"front_matter","blog":{"id":"f0m0e38","title":"Front Matter","description":"The
+        Front Matter Blog covers the intersection of science and technology since
+        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
+        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}}'
+  recorded_at: Wed, 06 Sep 2023 14:27:19 GMT
+- request:
+    method: get
+    uri: https://doi.org/10.5281/ZENODO.30799
+    body:
+      encoding: UTF-8
+      string: ''
+    headers:
+      Accept:
+      - application/vnd.citationstyles.csl+json
+      Connection:
+      - close
+      Host:
+      - doi.org
+      User-Agent:
+      - http.rb/5.1.1
+  response:
+    status:
+      code: 302
+      message: Found
+    headers:
+      Date:
+      - Wed, 06 Sep 2023 14:27:19 GMT
+      Content-Type:
+      - text/html;charset=utf-8
+      Content-Length:
+      - '183'
+      Connection:
+      - close
+      Location:
+      - https://data.crosscite.org/10.5281%2FZENODO.30799
+      Vary:
+      - Accept
+      Expires:
+      - Wed, 06 Sep 2023 15:22:17 GMT
+      Permissions-Policy:
+      - interest-cohort=(),browsing-topics=()
+      Cf-Cache-Status:
+      - DYNAMIC
+      Report-To:
+      - '{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=HfJ%2FINqIlNf1clkRNyNk1w4kyj2tWeLv%2Fk%2Bq1TPJfiWesgUC5k0QZJKvdec6chW%2BuxaeEQ8k1ha4KbZHFSOoWJ5MaWcPBNTbY0P3dcIeKDW6Jngg%2Bmm2V%2Bs%3D"}],"group":"cf-nel","max_age":604800}'
+      Nel:
+      - '{"success_fraction":0,"report_to":"cf-nel","max_age":604800}'
+      Strict-Transport-Security:
+      - max-age=31536000; includeSubDomains; preload
+      Server:
+      - cloudflare
+      Cf-Ray:
+      - 80276460fd026907-FRA
+      Alt-Svc:
+      - h3=":443"; ma=86400
+    body:
+      encoding: UTF-8
+      string: |-
+        <html><head><title>Handle Redirect</title></head>
+        <body><a href="https://data.crosscite.org/10.5281%2FZENODO.30799">https://data.crosscite.org/10.5281%2FZENODO.30799</a></body></html>
+  recorded_at: Wed, 06 Sep 2023 14:27:19 GMT
+- request:
+    method: get
+    uri: https://data.crosscite.org/10.5281%2FZENODO.30799
+    body:
+      encoding: UTF-8
+      string: ''
+    headers:
+      Accept:
+      - application/vnd.citationstyles.csl+json
+      Connection:
+      - close
+      User-Agent:
+      - http.rb/5.1.1
+      Host:
+      - data.crosscite.org
+  response:
+    status:
+      code: 200
+      message: OK
+    headers:
+      Date:
+      - Wed, 06 Sep 2023 14:27:21 GMT
+      Content-Type:
+      - application/vnd.citationstyles.csl+json; charset=utf-8
+      Transfer-Encoding:
+      - chunked
+      Connection:
+      - close
+      Status:
+      - 200 OK
+      Cache-Control:
+      - max-age=0, private, must-revalidate
+      Vary:
+      - Accept-Encoding, Origin
+      Etag:
+      - W/"808492baef8e3e4af0fa6812bc25a08c"
+      X-Runtime:
+      - '0.018245'
+      X-Request-Id:
+      - d5ae8229-4153-405b-9f97-9473171213d7
+      X-Powered-By:
+      - Phusion Passenger(R) 6.0.13
+      Server:
+      - nginx/1.18.0 + Phusion Passenger(R) 6.0.13
+    body:
+      encoding: UTF-8
+      string: |-
+        {
+          "type": "report",
+          "id": "https://doi.org/10.5281/zenodo.30799",
+          "categories": [
+            "persistent identifier",
+            "pid",
+            "orcid",
+            "doi",
+            "datacite"
+          ],
+          "author": [
+            {
+              "family": "Fenner",
+              "given": "Martin"
+            },
+            {
+              "family": "Demeranville",
+              "given": "Tom"
+            },
+            {
+              "family": "Kotarski",
+              "given": "Rachael"
+            },
+            {
+              "family": "Vision",
+              "given": "Todd"
+            },
+            {
+              "family": "Rueda",
+              "given": "Laura"
+            },
+            {
+              "family": "Dasler",
+              "given": "Robin"
+            },
+            {
+              "family": "Haak",
+              "given": "Laure"
+            },
+            {
+              "family": "Cruse",
+              "given": "Patricia"
+            }
+          ],
+          "issued": {
+            "date-parts": [
+              [
+                2015,
+                9,
+                11
+              ]
+            ]
+          },
+          "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.",
+          "DOI": "10.5281/ZENODO.30799",
+          "publisher": "Zenodo",
+          "title": "D2.1: Artefact, Contributor, And Organisation Relationship Data Schema",
+          "URL": "https://zenodo.org/record/30799",
+          "copyright": "Creative Commons Attribution 4.0"
+        }
+  recorded_at: Wed, 06 Sep 2023 14:27:21 GMT
+- request:
+    method: head
+    uri: https://doi.org/10.5438/bc11-cqw1
+    body:
+      encoding: UTF-8
+      string: ''
+    headers:
+      Connection:
+      - close
+      Host:
+      - doi.org
+      User-Agent:
+      - http.rb/5.1.1
+  response:
+    status:
+      code: 302
+      message: Found
+    headers:
+      Date:
+      - Wed, 06 Sep 2023 14:27:21 GMT
+      Content-Type:
+      - text/html;charset=utf-8
+      Content-Length:
+      - '233'
+      Connection:
+      - close
+      Location:
+      - https://datacite.org/blog/differences-between-orcid-and-datacite-metadata/
+      Vary:
+      - Accept
+      Expires:
+      - Wed, 06 Sep 2023 14:34:12 GMT
+      Permissions-Policy:
+      - interest-cohort=(),browsing-topics=()
+      Cf-Cache-Status:
+      - DYNAMIC
+      Report-To:
+      - '{"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=WlCur2YM%2BnSuhBmd%2BuAH%2BXnUzDOrP1HOBpYF%2F62pmS9GkIuLLkbrvgyL98NNnuKEjcjkjgP9qrwQCNM0x6%2FgmMkSI4uUT3fScDcp0lyCAJiy89on5cvGk3U%3D"}],"group":"cf-nel","max_age":604800}'
+      Nel:
+      - '{"success_fraction":0,"report_to":"cf-nel","max_age":604800}'
+      Strict-Transport-Security:
+      - max-age=31536000; includeSubDomains; preload
+      Server:
+      - cloudflare
+      Cf-Ray:
+      - 8027646d0cba9176-FRA
+      Alt-Svc:
+      - h3=":443"; ma=86400
+    body:
+      encoding: UTF-8
+      string: ''
+  recorded_at: Wed, 06 Sep 2023 14:27:21 GMT
+recorded_with: VCR 6.2.0

data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/ghost_post_without_doi.yml

@@ -23,13 +23,13 @@ http_interactions:
       Cache-Control:
       - public, max-age=0, must-revalidate
       Content-Length:
-      - '1654'
+      - '13845'
       Content-Type:
       - application/json; charset=utf-8
       Date:
-      - Mon, 10 Jul 2023 21:04:52 GMT
+      - Wed, 06 Sep 2023 14:27:16 GMT
       Etag:
-      - '"pkkw16ms8919y"'
+      - '"9vk0oiu0agaob"'
       Server:
       - Vercel
       Strict-Transport-Security:
@@ -39,7 +39,7 @@ http_interactions:
       X-Vercel-Cache:
       - MISS
       X-Vercel-Id:
-      - fra1::iad1::q9hc8-1689023092238-8f72026f2bf3
+      - fra1::iad1::2nsgw-1694010435634-7ef529f76f47
       Connection:
       - close
     body:
@@ -47,13 +47,146 @@ http_interactions:
       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
         Residency Visual Abstract","summary":"My prototype for a Residency Visual
         AbstractThis tool represents my own ideas and is not currently in use or endorsed
-        by any institution.Medical students applying to residency often have to grapple
+        by any institution. Medical students applying to residency often have to grapple
         with an incredible amount of information when evaluating prospective training
         programs. The increased number of applications and interviews inherent to
-        the Zoom era further exacerbates this issue. At the same time, programs need
-        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
-        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
-        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
-        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}}'
-  recorded_at: Mon, 10 Jul 2023 21:04:52 GMT
+        the Zoom era further exacerbates this issue.","content_html":"<figure><img
+        src=\"https://www.ideasurg.pub/content/images/2023/04/Residency-Scorecard-Light-Mode--7-.png\"
+        loading=\"lazy\" width=\"2000\" height=\"1127\" srcset=\"https://www.ideasurg.pub/content/images/size/w600/2023/04/Residency-Scorecard-Light-Mode--7-.png
+        600w, https://www.ideasurg.pub/content/images/size/w1000/2023/04/Residency-Scorecard-Light-Mode--7-.png
+        1000w, https://www.ideasurg.pub/content/images/size/w1600/2023/04/Residency-Scorecard-Light-Mode--7-.png
+        1600w, https://www.ideasurg.pub/content/images/size/w2400/2023/04/Residency-Scorecard-Light-Mode--7-.png
+        2400w\" /><figcaption>My prototype for a Residency Visual Abstract</figcaption></figure><div><div>This
+        tool represents my own ideas and is not currently in use or endorsed by any
+        institution.</div></div><p>Medical students applying to residency often have
+        to grapple with an incredible amount of information when evaluating prospective
+        training programs. The increased number of applications and interviews inherent
+        to the Zoom era further exacerbates this issue. At the same time, programs
+        need to find ways to communicate a great deal of information to applicants.
+        Due to the proliferation of social media, this communication is both more
+        extensive and more longitudinal than a one hour presentation on interview
+        day.</p><p>The traditional interview day presentation is a slide presentation
+        that provides several factual details about a program. While each program
+        is slightly different, most of these presentations cover common ground - including
+        where residents rotate, what services they do, where alumni match into fellowship,
+        examination pass rates, and information on professional development and research
+        activities. These presentations can often be long (I once helped edit a slide
+        deck that had 60 slides in it!) and difficult to recall. Furthermore, updating
+        these slides from year to year is a time consuming challenge. Finally, most
+        of these presentations are done in a traditional bullet point format with
+        few slides reserved for photos. Few are designed in a way that optimizes user
+        experience.</p><p>In my opinion, the most important quality of the program
+        is how well a prospective applicant fits in with the resident culture. Though
+        it is impossible to put into numbers, it has an outsized impact on a resident''s
+        experience and wellness. Furthermore, it is even harder to intuit in the absence
+        of an in-person interview experience. Nevertheless, there are important quantitative
+        metrics that applicants consider and programs want to showcase. However, there
+        is not yet a standardized, accessible, and visually appealing format to do
+        so. Given the challenges in communicating these details as well as the growing
+        power of social media , I wanted to design a new way that programs can effectively
+        and efficiently display and disseminate this information so that applicants
+        can be more informed and programs can better utilize their interview days
+        to convey the critical intangibles.</p><p>In the distinct but not quite distant
+        field of surgical research, the visual abstract has already proven to be an
+        excellent means of distilling a research study filled with details into an
+        easy-to-digest and visually pleasing format. Developed by Dr. Andrew Ibrahim
+        and colleagues, the visual abstract has already been adopted by 50 journals,
+        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>
+        that the presence of a visual abstract can more than double article visits
+        and increase impressions more than seven-fold. An excellent primer discussing
+        how to develop a visual abstract and highlighting its use in academic journals
+        is available <a href=\"https://static1.squarespace.com/static/5854aaa044024321a353bb0d/t/5a527aa89140b76bbfb2028a/1515354827682/VisualAbstract_Primer_v4_1.pdf?ref=ideasurg.pub\">here</a>.
+        </p><p>A variant of the visual abstract has also been used by residency programs
+        on social media in the past. An example from the Duke Surgery Residency program
+        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>
+        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>
+        <a href=\"https://twitter.com/hashtag/VisualAbstract?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#VisualAbstract</a>
+        <a href=\"https://twitter.com/hashtag/ByTheNumbers?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#ByTheNumbers</a>.
+        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>
+        at <a href=\"https://twitter.com/DukeSurgery?ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">@DukeSurgery</a>.
+        <a href=\"https://twitter.com/hashtag/SabistonSquad?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#SabistonSquad</a>
+        <a href=\"https://twitter.com/hashtag/SurgTwitter?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#SurgTwitter</a>
+        <a href=\"https://twitter.com/hashtag/MedTwitter?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#MedTwitter</a>
+        <a href=\"https://twitter.com/hashtag/SurgEd?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#SurgEd</a>
+        <a href=\"https://twitter.com/hashtag/ILookLikeASurgeon?src=hash&amp;ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">#ILookLikeASurgeon</a>
+        <a href=\"https://t.co/6ZqnfFrWE5?ref=ideasurg.pub\">pic.twitter.com/6ZqnfFrWE5</a></p>—
+        Duke General Surgery Residency (@DukeSurgRes) <a href=\"https://twitter.com/DukeSurgRes/status/1587460003941810179?ref_src=twsrc%5Etfw&amp;ref=ideasurg.pub\">November
+        1, 2022</a></blockquote>\n\n</figure><p>Inspired by this format, I tried to
+        design a version tailored towards prospective surgery trainees. I wanted to
+        see if I could boil down the complexity of a program into the fewest pieces
+        of data possible and present them in a user-friendly interface. </p><h3>The
+        Visual Abstract</h3><p>The abstract contains six different categories: demographics,
+        operative volume, education, research, fellowships, and other. The goal is
+        to capture relevant information regarding the tripartite mission of academic
+        surgery as well as understand a program''s strengths in diversity and inclusion
+        and career preparation. For each category, discrete data points were chosen
+        which can easily allow applicants to contextualize a program''s strengths
+        and weaknesses. The other category contains a checklist of features that applicants
+        seem to care about (based on observations and conversations though certainly
+        not proven scientifically). Finally, there is a space for QR codes to link
+        to the program website as well as a copy of the contract that matched applicants
+        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>
+        by the National Resident Matching Program).</p><p>Of course, the tool comes
+        with a dark mode!</p><figure><img src=\"https://www.ideasurg.pub/content/images/2023/04/Thumbnail--2-.png\"
+        loading=\"lazy\" width=\"1924\" height=\"1084\" srcset=\"https://www.ideasurg.pub/content/images/size/w600/2023/04/Thumbnail--2-.png
+        600w, https://www.ideasurg.pub/content/images/size/w1000/2023/04/Thumbnail--2-.png
+        1000w, https://www.ideasurg.pub/content/images/size/w1600/2023/04/Thumbnail--2-.png
+        1600w, https://www.ideasurg.pub/content/images/2023/04/Thumbnail--2-.png 1924w\"
+        /></figure><h3>What this is</h3><p>This visual abstract can provide a semi-standardized
+        format for programs to share important information with applicants allowing
+        them to compare important metrics in a comprehensive, “easy” way. It is important
+        to note that each of these data points is meant to be an objective measure
+        without any comment on its intrinsic value. For example, one program may have
+        a significantly higher case volume than peer institutions but less protected
+        education time. Another may have a robotic curriculum but not have any recent
+        chiefs who matched into Pediatric Surgery. None of these are independently
+        good or bad, but applicants should have an easy way to understand the factors
+        so that they can make the most informed decision. If a significant number
+        of programs adopt the visual abstract, it will naturally create incentives
+        for programs to share and improve on these metrics with transparency. In this
+        manner, healthy competition can actually generate an incentive to improve
+        program offerings for current residents as well (though this can have unintended
+        consequences…see limitations).</p><p>Some may question the wisdom of putting
+        these numbers out in the open - especially if they are not where a program
+        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>.
+        Many of these data points are already reported on during the interview process.
+        Moreover, most applicants want to know this information and value transparency.
+        Ultimately, no program is perfect, and how a program chooses to address perceived
+        strengths and weaknesses reflects its core values.</p><h3>What this is not
+        and other limitations</h3><p>No visual abstract, slide deck, or document will
+        be able to capture the full picture of a residency program - which at its
+        core is a collection of human beings. It is worth repeating that the most
+        important consideration students should make when choosing a program is missing
+        from this work. Furthermore, the exact data points used may not be correct.
+        At one point, I considered putting a box for ABSITE pass rate, however I thought
+        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>,
+        not a summative, assessment. Furthermore, there is no box specifying the number
+        of LGBTQ residents in a program. While this is an essential component of diversity,
+        equity, and inclusion, it was omitted due to the fact that some of these residents
+        may not be publicly out and this would lead to an inaccurate representation.
+        Another missing box is the number of residents with children, given that family
+        support is an increasingly recognized feature that students are looking for
+        in training programs.</p><p>I would like for this to be even less cluttered
+        - and user feedback can drive further reduction of content such that the distilled
+        final version is even more elegant. Currently, the vision for this project
+        is that of a grassroots project, where individual programs can choose to use,
+        improve, and modify this template to broadcast important information to applicants.
+        However, I am wary of the general principle that once quantitative metrics
+        are used by a central authority to rank, there is a natural tendency to gamify
+        those metrics whether or not the underlying feature they seek to estimate
+        is actually affected.</p><h3>What to do with this template</h3><p>In short,
+        whatever you would like. The template was built in Figma, which has become
+        the industry-standard in visual design. It is free to make a basic Figma account,
+        and the full suite of features is also available for free with proof of affiliation
+        with a university. Figma offers the ability to comment on a template as well
+        as duplicate or \"remix\" the template for personal use. I would appreciate
+        your feedback on how to make this template better. Moreover, I encourage you
+        to take it, modify it, improve it, and share your changes publicly. Together,
+        we can continue to iteratively design this initial prototype and develop a
+        robust, user-friendly tool that provides values to students, residents, and
+        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
+        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
+        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
+        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}}'
+  recorded_at: Wed, 06 Sep 2023 14:27:16 GMT
 recorded_with: VCR 6.2.0

data/spec/fixtures/vcr_cassettes/Commonmeta_Metadata/get_json_feed_item_metadata/jekyll_post.yml

@@ -23,13 +23,13 @@ http_interactions:
       Cache-Control:
       - public, max-age=0, must-revalidate
       Content-Length:
-      - '1781'
+      - '4387'
       Content-Type:
       - application/json; charset=utf-8
       Date:
-      - Mon, 10 Jul 2023 21:04:56 GMT
+      - Wed, 06 Sep 2023 14:24:39 GMT
       Etag:
-      - '"27g5bun4gu1df"'
+      - '"139wt2n3zw43d9"'
       Server:
       - Vercel
       Strict-Transport-Security:
@@ -39,7 +39,7 @@ http_interactions:
       X-Vercel-Cache:
       - MISS
       X-Vercel-Id:
-      - fra1::iad1::k2scp-1689023095925-56ecd54bbfbe
+      - fra1::iad1::ddxbj-1694010278585-063d4d41a9e8
       Connection:
       - close
     body:
@@ -49,13 +49,42 @@ http_interactions:
         Citation Style Language developers have worked to address a backlog of feature
         requests. This work will be reflected in two upcoming releases. The first
         of these, 1.0.2, is slated for release shortly. Its focus is on easy to implement,
-        non-controversial additions, principally new item types, fields, and terms.
-        We’re seeking public comment on the planned released from now until July 26,
-        2020, 12pm EDT. A non-technical summary of the release can be found in a google...","published_at":1594425600,"updated_at":1594425600,"indexed_at":1689006804,"authors":[{"url":null,"name":"Sebastian
-        Karcher"}],"image":null,"tags":[],"language":"en","reference":[],"blog_id":"prmb582","blog_name":"Citation
-        Style Language","blog":{"id":"prmb582","title":"Citation Style Language","description":"CitationStyles.org,
-        home of the Citation Style Language (CSL), a popular open XML-based language
-        to describe the formatting of citations and bibliographies.","language":"en","favicon":null,"feed_url":"https://citationstyles.org/feed.xml","home_page_url":"https://citationstyles.org/","user_id":"8498eaf6-8c58-4b58-bc15-27eda292b1aa","created_at":"2023-05-31T08:18:29+00:00","indexed_at":"2023-04-25","feed_format":"application/atom+xml","license":"https://creativecommons.org/licenses/by/4.0/legalcode","generator":"Jekyll
-        3.9.3","category":"Engineering and Technology","prefix":"10.59350","modified_at":"2020-07-11T00:00:00+00:00","version":"https://jsonfeed.org/version/1.1","backlog":false,"current_feed_url":null,"expired":null}}'
-  recorded_at: Mon, 10 Jul 2023 21:04:56 GMT
+        non-controversial additions, principally new item types, fields, and terms.","content_html":"<p>Over
+        the past few months, Citation Style Language developers have worked to address
+        a backlog of feature requests. This work will be reflected in two upcoming
+        releases. The first of these, 1.0.2, is slated for release shortly. Its focus
+        is on easy to implement, non-controversial additions, principally new item
+        types, fields, and terms. We’re seeking public comment on the planned released
+        from now until <strong>July 26, 2020, 12pm EDT</strong>.</p>\n\n<p>A non-technical
+        summary of the release can be found in a <a href=\"https://docs.google.com/document/d/1wY1cOOamDYYh8VNW7h_uleqieBDGOa_LYsRiVdQy1RI/edit#heading=h.wsywjzy5t4j6\">google
+        doc here</a>. For more technical details, you can follow the development on
+        the <a href=\"https://github.com/orgs/citation-style-language/projects/3\">github
+        project board</a>. We welcome feedback directly on the google doc, in specific
+        github issues, or on our <a href=\"https://discourse.citationstyles.org/\">forums</a>.</p>\n\n<p>Tremendous
+        thanks to Bruce D’Arcus, Denis Maier, and Brenton Wiernik, who did the bulk
+        of the work of organizing proposals accumulated over the last 8 years and
+        preparing the release.</p>\n\n<h2>Previewing CSL 1.1</h2>\n<p>CSL 1.1, slated
+        for release later this year, will include more significant extensions of CSL
+        functionality. While we’ll have a separate public comment period for this
+        release, we’re happy for input on the ongoing discussions on github and the
+        forums. In particular, we’re eager to hear from projects implementing CSL
+        styles, both in a citeproc and in user-facing applications such as reference
+        managers or citation formatters.</p>\n\n<p>This release will primarily add
+        the following new features:</p>\n<ul>\n  <li>Full support for narrative citation
+        styles (“Like Doe (2018)”).</li>\n  <li>Ability to specify more complex conditional
+        logic.</li>\n  <li>Ability to independently format subtitles and main titles.</li>\n  <li>A
+        new “related” attribute to express related reviewed and original items (still
+        in discussion).</li>\n  <li>Improvements to the CSL input format(s):\n    <ul>\n      <li>Adopting
+        the new EDTF ISO standard, which offers full support for date ranges, seasons,
+        uncertain and approximate qualifiers, and decades and centuries.</li>\n      <li>A
+        new “custom” property to add extension metadata.</li>\n      <li>New related
+        modelling to match the new style attribute (as above, still in discussion).</li>\n      <li>An
+        official YAML representation, which can be validated with the same JSON schemas.</li>\n    </ul>\n  </li>\n</ul>","published_at":1594425600,"updated_at":1594425600,"indexed_at":1693251839,"authors":[{"url":"https://orcid.org/0000-0001-8249-7388","name":"Sebastian
+        Karcher"}],"image":null,"tags":[],"language":"en","reference":[],"relationships":[],"blog_id":"prmb582","blog_name":"Citation
+        Style Language","blog_slug":"csl","blog":{"id":"prmb582","title":"Citation
+        Style Language","description":"CitationStyles.org, home of the Citation Style
+        Language (CSL), a popular open XML-based language to describe the formatting
+        of citations and bibliographies.","language":"en","favicon":"https://citationstyles.org/assets/img/csl-logo-small-inverse-150.png","feed_url":"https://citationstyles.org/feed.xml","home_page_url":"https://citationstyles.org","user_id":"9812a172-7dd2-481a-a82a-50e6ac61da06","created_at":"2023-04-25","feed_format":"application/atom+xml","license":"https://creativecommons.org/licenses/by/4.0/legalcode","generator":"Jekyll
+        3.9.3","category":"computerAndInformationSciences","prefix":"10.59350","modified_at":"2020-07-11T00:00:00+00:00","version":"https://jsonfeed.org/version/1.1","current_feed_url":null,"status":"active","issn":null,"backlog":0,"authors":null,"plan":"Starter","slug":"csl","use_mastodon":false}}'
+  recorded_at: Wed, 06 Sep 2023 14:24:39 GMT
 recorded_with: VCR 6.2.0