commonmeta-schema 1.0rc2.dev6__tar.gz → 1.0rc2.dev7__tar.gz

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 (85) hide show
  1. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/PKG-INFO +1 -1
  2. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/jsonfeed_cczero_license.json +10 -10
  3. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/jsonfeed_ghost_with_affiliations.json +16 -10
  4. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/jsonfeed_post_with_funding.json +18 -27
  5. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/jsonfeed_post_with_relationships.json +24 -18
  6. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/jsonfeed_wordpress_with_references.json +10 -10
  7. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/pyproject.toml +1 -1
  8. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/.gitignore +0 -0
  9. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/LICENSE +0 -0
  10. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/README.md +0 -0
  11. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/bibtex/crossref.bib +0 -0
  12. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/bibtex/journal_article.bib +0 -0
  13. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/bibtex/pure.bib +0 -0
  14. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/bibtex_commonmeta/crossref.json +0 -0
  15. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/bibtex_commonmeta/journal_article.json +0 -0
  16. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/bibtex_out/journal_article.bib +0 -0
  17. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/cff/CITATION.cff +0 -0
  18. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/cff_commonmeta/CITATION.json +0 -0
  19. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/codemeta/codemeta.json +0 -0
  20. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/blog_post_1.json +0 -0
  21. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/citeproc.json +0 -0
  22. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/citeproc_no_author.json +0 -0
  23. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/codemeta.json +0 -0
  24. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/crossref_journal_article.json +0 -0
  25. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/csl_journal_article.json +0 -0
  26. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/datacite_blog_post.json +0 -0
  27. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/datacite_blog_post_citeproc.json +0 -0
  28. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/datacite_dataset.json +0 -0
  29. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/datacite_date.json +0 -0
  30. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/datacite_dryad.json +0 -0
  31. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/datacite_multiple_identifiers.json +0 -0
  32. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/datacite_subject_scheme_for.json +0 -0
  33. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/dataset_geo.json +0 -0
  34. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/inveniordm_software.json +0 -0
  35. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/journal_article.json +0 -0
  36. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/journal_article_datacite_reader.json +0 -0
  37. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/jsonfeed_blog_post.json +0 -0
  38. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/jsonfeed_blog_post_sathe.json +0 -0
  39. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/schemaorg_blog_posting.json +0 -0
  40. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/schemaorg_geolocation.json +0 -0
  41. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/schemaorg_gtex.json +0 -0
  42. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/commonmeta/schemaorg_journal_article.json +0 -0
  43. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/crossref/crossref_journal_article.json +0 -0
  44. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/crossref_out/crossref_journal_article.json +0 -0
  45. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/crossref_xml/crossref_elife_01567.xml +0 -0
  46. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/crossref_xml/journal_article.xml +0 -0
  47. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/crossref_xml_commonmeta/crossref_elife_01567.json +0 -0
  48. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/csl/citeproc.json +0 -0
  49. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/csl/citeproc_no_author.json +0 -0
  50. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/csl/csl_journal_article.json +0 -0
  51. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite/journal_article.json +0 -0
  52. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_reader/datacite_blog_post.json +0 -0
  53. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_reader/datacite_blog_post_citeproc.json +0 -0
  54. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_reader/datacite_dataset.json +0 -0
  55. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_reader/datacite_date.json +0 -0
  56. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_reader/datacite_dryad.json +0 -0
  57. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_reader/datacite_multiple_identifiers.json +0 -0
  58. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_reader/datacite_subject_scheme_for.json +0 -0
  59. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_reader/journal_article_datacite_reader.json +0 -0
  60. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_xml/full_v4_4.xml +0 -0
  61. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_xml/geolocation.xml +0 -0
  62. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_xml/schema_4_0.xml +0 -0
  63. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_xml_commonmeta/full_v4_4.json +0 -0
  64. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_xml_commonmeta/geolocation.json +0 -0
  65. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/datacite_xml_commonmeta/schema_4_0.json +0 -0
  66. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/inveniordm/inveniordm_software.json +0 -0
  67. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/jsonfeed/jsonfeed_blog_post.json +0 -0
  68. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/jsonfeed/jsonfeed_blog_post_sathe.json +0 -0
  69. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/jsonfeed/jsonfeed_cczero_license.json +0 -0
  70. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/jsonfeed/jsonfeed_ghost_with_affiliations.json +0 -0
  71. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/jsonfeed/jsonfeed_post_with_funding.json +0 -0
  72. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/jsonfeed/jsonfeed_post_with_relationships.json +0 -0
  73. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/jsonfeed/jsonfeed_wordpress_with_references.json +0 -0
  74. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/ris/crossref.ris +0 -0
  75. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/ris/pure.ris +0 -0
  76. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/ris_commonmeta/crossref.json +0 -0
  77. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/schemaorg/schemaorg_blog_posting.json +0 -0
  78. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/schemaorg/schemaorg_geolocation.json +0 -0
  79. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/schemaorg/schemaorg_gtex.json +0 -0
  80. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/schemaorg/schemaorg_journal_article.json +0 -0
  81. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/fixtures/schemaorg_out/journal_article.json +0 -0
  82. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/schemas/commonmeta_v1.0rc1.json +0 -0
  83. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/schemas/commonmeta_v1.0rc2.json +0 -0
  84. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/src/commonmeta_schema/__init__.py +0 -0
  85. {commonmeta_schema-1.0rc2.dev6 → commonmeta_schema-1.0rc2.dev7}/src/commonmeta_schema/resources.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: commonmeta-schema
3
- Version: 1.0rc2.dev6
3
+ Version: 1.0rc2.dev7
4
4
  Summary: Commonmeta JSON Schemas and conformance fixtures
5
5
  Project-URL: Homepage, https://github.com/front-matter/commonmeta-schema
6
6
  Project-URL: Repository, https://github.com/front-matter/commonmeta-schema
@@ -2,12 +2,11 @@
2
2
  "id": "https://doi.org/10.59350/xgwqt-1sq35",
3
3
  "type": "BlogPost",
4
4
  "container": {
5
- "identifier": "https://rogue-scholar.org/blogs/cameronneylon",
6
- "identifier_type": "URL",
7
5
  "type": "Blog",
8
- "title": "Science in the Open"
6
+ "title": "Science in the Open",
7
+ "identifier": "https://rogue-scholar.org/blogs/cameronneylon",
8
+ "identifier_type": "URL"
9
9
  },
10
- "content": "<p><em>Consider this yet another commitment to trying to write here a little more regularly. Lots of thinking has been going on but not much writing! At least not writing as I&#8217;m going&#8230;</em></p>\n\n\n\n<p>Three things colliding over the past few weeks have led me to want to try and get some ideas down. The first was a conversation – one of a set really – with Titus Brown and Dan Katz relating to the application of political economy and collective action theory to communities building research. <br></p>\n\n\n\n<p>The second was the posting of video of a talk I gave a month or so back to our research centre, the Centre for Culture and Technology at Curtin University. In this, I tried to work through the full story of some recent thinking for the first time. I&#8217;m trying to articulate what has evolved in my thinking from a view driven by network theory that open is good, more open is better, to an understanding of where and how things have gone wrong.</p>\n\n\n\n<p>The final piece was the publication of a new paper (<a href=\"http://philsci-archive.pitt.edu/14352/\">preprint version is also available</a>, actually its what I read so that&#8217;s what I&#8217;ll link to) by Sabina Leonelli which tackles the value of reproducibility as a concept head on. Leonelli&#8217;s work has been a big influence on my developing thinking. Two pieces are particularly relevant. The <a href=\"https://books.google.co.uk/books?hl=en&amp;lr=&amp;id=i8NADQAAQBAJ&amp;oi=fnd&amp;pg=PR5&amp;dq=sabina+leonelli&amp;ots=iBvrf8uB3L&amp;sig=I5cdiwlIRoZQrm7iX2ksRe70ias&amp;redir_esc=y#v=onepage&amp;q=sabina%20leonelli&amp;f=false\">idea that data is not a thing, but is a category defined by use</a>. That is, we can&#8217;t say whether a particular object <em>is</em> data, only that something is data when it is used in particular ways. This is true of many things in research, the objectivist in us wants the qualities of objects like data, methods, and knowledge itself to be eternal platonic concepts inherent in the objects themselves. In practice however these qualities only reveal themselves in certain activities.</p>\n\n\n\n<p>These activities depend in turn on &#8216;repertoires&#8217; another concept I&#8217;ve taken from Leonelli&#8217;s work, this time from <a href=\"https://doi.org/10.1016/j.shpsa.2016.08.003\">a paper published with Rachel Ankeny</a>. The concept here is that research communities are defined by practices and that these practices are not just learned, but displayed and internalised, in a similar manner to a musician learning repertoire as a set of hurdles to be jumped in their development. I first read this paper at the same time as I was reading <a href=\"https://www.amazon.co.uk/Situated-Learning-Participation-Computational-Perspectives/dp/0521413087/\">Lave and Wenger&#8217;s </a><em><a href=\"https://www.amazon.co.uk/Situated-Learning-Participation-Computational-Perspectives/dp/0521413087/\">Situated Learning</a></em> and the parallel between craft learning (see also <a href=\"https://www.amazon.com/Scientific-Knowledge-Its-Social-Problems/dp/1560008512\">Ravetz</a>), identity making (see also <a href=\"https://www.bloomsbury.com/uk/cultural-science-9781849666022/\">Hartley and Potts</a>) and community had a significant resonance for me.</p>\n\n\n\n<p>In the new piece Leonelli tackles the range of different, and largely incommensurate meanings that are ascribed to the concept of &#8216;reproducibility&#8217;. The paper tackles a range of disciplinarily bound practices ranging from computational sciences, where there is &#8216;total control&#8217; (yes I could quibble about machine states and compilers but this is philosophy, let&#8217;s accept the abstraction) through to ethnography, where there is the expectation that the life experience of the researcher affects the outcome, and that a different researcher would reach different conclusions.</p>\n\n\n\n<p>The article focuses on how the necessity for documentation changes as different aspects of <em>accountability</em> rather than reproducibility are taken into account. These concepts of responsibility and accountability for sources of variability that have implications for the claims being made seems more productive and more readily contextualised and generalised. The article finishes with a call to value &#8216;epistemic diversity&#8217;. That is, it is through differing kinds of cross referencing, with different sources of variability, accountability, and reliability that we can most usefully build knowledge.</p>\n\n\n\n<p>All of this resonates for me because I&#8217;ve been working towards a similar end from a different place. My concern has been thinking about how to operationalise social models of knowledge production. There are a broad class of constructivist models of knowledge where validation occurs when groups come together and contest claims. I have a paper currently in review that casts this as &#8216;productive conflict&#8217;.</p>\n\n\n\n<p>In such models the greater the diversity of groups in contact the more &#8216;general&#8217; the knowledge that is created. However the more diverse those groups are, the less likely it is that such contact will be productive. Indeed it can be harmful – and in most cases involving disadvantaged groups (which is practically everyone in comparison to a professional, permanently employed, western academic) it is at the very least a significant burden and frequently significantly damaging.</p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"Cameron Neylon - Network Enabled Scholarship: Connectivity, groups and growth in the production ...\" width=\"525\" height=\"295\" src=\"https://www.youtube.com/embed/9wvEh1Rn4-8?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen></iframe>\n</div></figure>\n\n\n\n<p>In the talk I&#8217;m trying to work through the question of how such contacts can be made safe, while equally privileging the value of closing ranks, returning to community to regain strength and re-affirm identity. If diversity is a first order principle in the utilitarian goal of making knowledge, what are the principles of care that allow us to protect the communities that contribute that diversity? </p>\n\n\n\n<p>Part of the argument I make is that we need to return to the thinking about network structures. Five years ago I was making the case that &#8216;bigger is better&#8217; underpinned by an assumption that even if benefits flowed to those who were already well connected the new opportunities of scale would still spread benefits more widely. That seems less and less to be the case today, and the key problems appear to be ones where the benefits of locality are reduced or broken, boundaries are too readily traversed, and groups come into contact in <em>non-productive</em> conflict too frequently.</p>\n\n\n\n<iframe loading=\"lazy\" src=\"//www.slideshare.net/slideshow/embed_code/key/BibYCjjYUQdN13?startSlide=94\" width=\"595\" height=\"485\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" style=\"border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;\" allowfullscreen> </iframe>\n\n\n\n<p>In the talk I discuss the need to privilege locality. This is the opposite of what most of our systems do today, both in the wider world (&#8216;you need to go viral!&#8217;) and in academia (&#8216;international rankings! international journals!&#8217;). Many social models draw simple lines with groups inside or outside. Even with a mental view of groups within groups and overlapping groups this tends to miss the messiness that results from non-homogenous interactions across group boundaries. Network structural analysis is harder to do and harder to visualise but it seems to me crucial to get a view of what the optimal dynamics are.</p>\n\n\n\n<p>One way to frame the question of network and community dynamics is economically. That is, to ask how the differing groups and communities in contact are sustained and succeed or fail. This in turn is a question of exchange (not necessarily purely financial exchange, but there are limitations to this framing!). Models of club economics and collective action from political economy are useful here and this leads us back to the first conversation I mentioned above.</p>\n\n\n\n<p>Titus Brown has been working through <a href=\"http://ivory.idyll.org/blog/tag/cpr.html\">a series of posts</a>, relating to the NIH Data Commons project looking at the goods produced in open source projects through the lens of commons and clubs goods. Dan Katz was raising good questions about issues of time and scale that are not well captured by the classical analysis of goods.</p>\n\n\n\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\"><div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\" data-width=\"525\" data-dnt=\"true\"><p lang=\"en\" dir=\"ltr\">Chatting with @egonwillighagen and <a href=\"https://twitter.com/derkarts?ref_src=twsrc%5Etfw\">@derkarts</a> yesterday, drew this diagram of club/public/private goods and they asked me to tweet it &#8211; so here it is! see also <a href=\"https://t.co/8pmGIBEak4\">https://t.co/8pmGIBEak4</a> <a href=\"https://twitter.com/hashtag/commonspilot?src=hash&amp;ref_src=twsrc%5Etfw\">#commonspilot</a> <a href=\"https://t.co/RbBoTCLGVr\">pic.twitter.com/RbBoTCLGVr</a></p>&mdash; Titus Brown (@ctitusbrown) <a href=\"https://twitter.com/ctitusbrown/status/1047409685001904134?ref_src=twsrc%5Etfw\">October 3, 2018</a></blockquote><script async src=\"https://platform.twitter.com/widgets.js\" charset=\"utf-8\"></script>\n</div></figure>\n\n\n\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\"><div class=\"wp-block-embed__wrapper\">\nhttps://twitter.com/danielskatz/status/1047442062264717312\n</div></figure>\n\n\n\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\"><div class=\"wp-block-embed__wrapper\">\nhttps://twitter.com/danielskatz/status/1047449426564960256\n</div></figure>\n\n\n\n<p>I have quibbles with Brown&#8217;s analyses and often with others who use this kind of goods-class analysis. However I only just realised that my issue was similar to Leonelli&#8217;s point about data. The question of what is &#8216;the good&#8217; in any particular case is relational, not an absolute. Our discussion of these models tends to turn on an implicit assumption that something (prestige, code, knowledge, expert attention) is the specific good in play, something that in turn surfaces a common assumption in most classical economics that it is appropriate to assume some kind of &#8216;numeraire good&#8217; that allows exchange of all the others (this is what money is for, and if there&#8217;s anything wrong with economic analysis, its money..). </p>\n\n\n\n<p>This doesn&#8217;t leave me with any firm conclusions beyond some possible routes to analysis. It seems likely that simple analysis based on static descriptions of community and the environment aren&#8217;t going to give us answers. We need to understand dynamics of groups opening up and enclosing over time, what sustains them, and what they might find valuable in exchange. We need agent based modelling of the network structures these occur over, and ways of translating from local structure in networks to more &#8216;bright-lined&#8217; social models of groups. We need to move beyond the simple &#8216;economic mathematics&#8217; that is often developed from the the club economics of Buchannan and Olson and to develop much more sophisticated and flexible models that allow the nature of exchange and goods to change when viewed from different perspectives.</p>\n\n\n\n<p>All in all it emphasises the conclusion I&#8217;d reached, that diversity is a first order principle. All forms of diversity and the more diverse the better, provided the coordination between groups is principled. There&#8217;s a lot to unpack in that word &#8216;principled&#8217; but I feel like its the link to the ethical dimension I&#8217;ve been missing. I need to dig deeper into notions of &#8216;care&#8217; (Moore, Priego) and &#8216;flourishing&#8217; (Holbrook) to tease this out. <br></p>",
11
10
  "contributors": [
12
11
  {
13
12
  "type": "Person",
@@ -17,9 +16,9 @@
17
16
  "family_name": "Neylon",
18
17
  "affiliations": [
19
18
  {
20
- "name": "Curtin University",
21
19
  "identifier": "https://ror.org/02n415q13",
22
- "identifier_type": "ROR"
20
+ "identifier_type": "ROR",
21
+ "name": "Curtin University"
23
22
  }
24
23
  ]
25
24
  },
@@ -28,6 +27,7 @@
28
27
  ]
29
28
  }
30
29
  ],
30
+ "title": "Epistemic diversity and knowledge production",
31
31
  "date_published": "2018-10-23T00:00:00Z",
32
32
  "date_updated": "2025-12-08T10:41:22Z",
33
33
  "description": "Consider this yet another commitment to trying to write here a little more regularly. Lots of thinking has been going on but not much writing! At least not writing as I'm going… Three things colliding over the past few weeks have led me to want to try and get some ideas down.",
@@ -53,7 +53,6 @@
53
53
  "type": "IsPartOf"
54
54
  }
55
55
  ],
56
- "schema_version": "https://commonmeta.org/commonmeta_v1.0rc2.json",
57
56
  "subjects": [
58
57
  {
59
58
  "id": "https://openalex.org/subfields/1802",
@@ -63,7 +62,8 @@
63
62
  "subject": "CCC"
64
63
  }
65
64
  ],
66
- "title": "Epistemic diversity and knowledge production",
67
- "url": "https://cameronneylon.net/blog/epistemic-diversity-and-knowledge-production",
68
- "version": "v1"
65
+ "url": "https://cameronneylon.net/blog/epistemic-diversity-and-knowledge-production/",
66
+ "version": "v1",
67
+ "content": "<p><em>Consider this yet another commitment to trying to write here a little more regularly. Lots of thinking has been going on but not much writing! At least not writing as I&#8217;m going&#8230;</em></p>\n\n\n\n<p>Three things colliding over the past few weeks have led me to want to try and get some ideas down. The first was a conversation – one of a set really – with Titus Brown and Dan Katz relating to the application of political economy and collective action theory to communities building research. <br></p>\n\n\n\n<p>The second was the posting of video of a talk I gave a month or so back to our research centre, the Centre for Culture and Technology at Curtin University. In this, I tried to work through the full story of some recent thinking for the first time. I&#8217;m trying to articulate what has evolved in my thinking from a view driven by network theory that open is good, more open is better, to an understanding of where and how things have gone wrong.</p>\n\n\n\n<p>The final piece was the publication of a new paper (<a href=\"http://philsci-archive.pitt.edu/14352/\">preprint version is also available</a>, actually its what I read so that&#8217;s what I&#8217;ll link to) by Sabina Leonelli which tackles the value of reproducibility as a concept head on. Leonelli&#8217;s work has been a big influence on my developing thinking. Two pieces are particularly relevant. The <a href=\"https://books.google.co.uk/books?hl=en&amp;lr=&amp;id=i8NADQAAQBAJ&amp;oi=fnd&amp;pg=PR5&amp;dq=sabina+leonelli&amp;ots=iBvrf8uB3L&amp;sig=I5cdiwlIRoZQrm7iX2ksRe70ias&amp;redir_esc=y#v=onepage&amp;q=sabina%20leonelli&amp;f=false\">idea that data is not a thing, but is a category defined by use</a>. That is, we can&#8217;t say whether a particular object <em>is</em> data, only that something is data when it is used in particular ways. This is true of many things in research, the objectivist in us wants the qualities of objects like data, methods, and knowledge itself to be eternal platonic concepts inherent in the objects themselves. In practice however these qualities only reveal themselves in certain activities.</p>\n\n\n\n<p>These activities depend in turn on &#8216;repertoires&#8217; another concept I&#8217;ve taken from Leonelli&#8217;s work, this time from <a href=\"https://doi.org/10.1016/j.shpsa.2016.08.003\">a paper published with Rachel Ankeny</a>. The concept here is that research communities are defined by practices and that these practices are not just learned, but displayed and internalised, in a similar manner to a musician learning repertoire as a set of hurdles to be jumped in their development. I first read this paper at the same time as I was reading <a href=\"https://www.amazon.co.uk/Situated-Learning-Participation-Computational-Perspectives/dp/0521413087/\">Lave and Wenger&#8217;s </a><em><a href=\"https://www.amazon.co.uk/Situated-Learning-Participation-Computational-Perspectives/dp/0521413087/\">Situated Learning</a></em> and the parallel between craft learning (see also <a href=\"https://www.amazon.com/Scientific-Knowledge-Its-Social-Problems/dp/1560008512\">Ravetz</a>), identity making (see also <a href=\"https://www.bloomsbury.com/uk/cultural-science-9781849666022/\">Hartley and Potts</a>) and community had a significant resonance for me.</p>\n\n\n\n<p>In the new piece Leonelli tackles the range of different, and largely incommensurate meanings that are ascribed to the concept of &#8216;reproducibility&#8217;. The paper tackles a range of disciplinarily bound practices ranging from computational sciences, where there is &#8216;total control&#8217; (yes I could quibble about machine states and compilers but this is philosophy, let&#8217;s accept the abstraction) through to ethnography, where there is the expectation that the life experience of the researcher affects the outcome, and that a different researcher would reach different conclusions.</p>\n\n\n\n<p>The article focuses on how the necessity for documentation changes as different aspects of <em>accountability</em> rather than reproducibility are taken into account. These concepts of responsibility and accountability for sources of variability that have implications for the claims being made seems more productive and more readily contextualised and generalised. The article finishes with a call to value &#8216;epistemic diversity&#8217;. That is, it is through differing kinds of cross referencing, with different sources of variability, accountability, and reliability that we can most usefully build knowledge.</p>\n\n\n\n<p>All of this resonates for me because I&#8217;ve been working towards a similar end from a different place. My concern has been thinking about how to operationalise social models of knowledge production. There are a broad class of constructivist models of knowledge where validation occurs when groups come together and contest claims. I have a paper currently in review that casts this as &#8216;productive conflict&#8217;.</p>\n\n\n\n<p>In such models the greater the diversity of groups in contact the more &#8216;general&#8217; the knowledge that is created. However the more diverse those groups are, the less likely it is that such contact will be productive. Indeed it can be harmful – and in most cases involving disadvantaged groups (which is practically everyone in comparison to a professional, permanently employed, western academic) it is at the very least a significant burden and frequently significantly damaging.</p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"Cameron Neylon - Network Enabled Scholarship: Connectivity, groups and growth in the production ...\" width=\"525\" height=\"295\" src=\"https://www.youtube.com/embed/9wvEh1Rn4-8?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen></iframe>\n</div></figure>\n\n\n\n<p>In the talk I&#8217;m trying to work through the question of how such contacts can be made safe, while equally privileging the value of closing ranks, returning to community to regain strength and re-affirm identity. If diversity is a first order principle in the utilitarian goal of making knowledge, what are the principles of care that allow us to protect the communities that contribute that diversity? </p>\n\n\n\n<p>Part of the argument I make is that we need to return to the thinking about network structures. Five years ago I was making the case that &#8216;bigger is better&#8217; underpinned by an assumption that even if benefits flowed to those who were already well connected the new opportunities of scale would still spread benefits more widely. That seems less and less to be the case today, and the key problems appear to be ones where the benefits of locality are reduced or broken, boundaries are too readily traversed, and groups come into contact in <em>non-productive</em> conflict too frequently.</p>\n\n\n\n<iframe loading=\"lazy\" src=\"//www.slideshare.net/slideshow/embed_code/key/BibYCjjYUQdN13?startSlide=94\" width=\"595\" height=\"485\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" style=\"border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;\" allowfullscreen> </iframe>\n\n\n\n<p>In the talk I discuss the need to privilege locality. This is the opposite of what most of our systems do today, both in the wider world (&#8216;you need to go viral!&#8217;) and in academia (&#8216;international rankings! international journals!&#8217;). Many social models draw simple lines with groups inside or outside. Even with a mental view of groups within groups and overlapping groups this tends to miss the messiness that results from non-homogenous interactions across group boundaries. Network structural analysis is harder to do and harder to visualise but it seems to me crucial to get a view of what the optimal dynamics are.</p>\n\n\n\n<p>One way to frame the question of network and community dynamics is economically. That is, to ask how the differing groups and communities in contact are sustained and succeed or fail. This in turn is a question of exchange (not necessarily purely financial exchange, but there are limitations to this framing!). Models of club economics and collective action from political economy are useful here and this leads us back to the first conversation I mentioned above.</p>\n\n\n\n<p>Titus Brown has been working through <a href=\"http://ivory.idyll.org/blog/tag/cpr.html\">a series of posts</a>, relating to the NIH Data Commons project looking at the goods produced in open source projects through the lens of commons and clubs goods. Dan Katz was raising good questions about issues of time and scale that are not well captured by the classical analysis of goods.</p>\n\n\n\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\"><div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\" data-width=\"525\" data-dnt=\"true\"><p lang=\"en\" dir=\"ltr\">Chatting with @egonwillighagen and <a href=\"https://twitter.com/derkarts?ref_src=twsrc%5Etfw\">@derkarts</a> yesterday, drew this diagram of club/public/private goods and they asked me to tweet it &#8211; so here it is! see also <a href=\"https://t.co/8pmGIBEak4\">https://t.co/8pmGIBEak4</a> <a href=\"https://twitter.com/hashtag/commonspilot?src=hash&amp;ref_src=twsrc%5Etfw\">#commonspilot</a> <a href=\"https://t.co/RbBoTCLGVr\">pic.twitter.com/RbBoTCLGVr</a></p>&mdash; Titus Brown (@ctitusbrown) <a href=\"https://twitter.com/ctitusbrown/status/1047409685001904134?ref_src=twsrc%5Etfw\">October 3, 2018</a></blockquote><script async src=\"https://platform.twitter.com/widgets.js\" charset=\"utf-8\"></script>\n</div></figure>\n\n\n\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\"><div class=\"wp-block-embed__wrapper\">\nhttps://twitter.com/danielskatz/status/1047442062264717312\n</div></figure>\n\n\n\n<figure class=\"wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter\"><div class=\"wp-block-embed__wrapper\">\nhttps://twitter.com/danielskatz/status/1047449426564960256\n</div></figure>\n\n\n\n<p>I have quibbles with Brown&#8217;s analyses and often with others who use this kind of goods-class analysis. However I only just realised that my issue was similar to Leonelli&#8217;s point about data. The question of what is &#8216;the good&#8217; in any particular case is relational, not an absolute. Our discussion of these models tends to turn on an implicit assumption that something (prestige, code, knowledge, expert attention) is the specific good in play, something that in turn surfaces a common assumption in most classical economics that it is appropriate to assume some kind of &#8216;numeraire good&#8217; that allows exchange of all the others (this is what money is for, and if there&#8217;s anything wrong with economic analysis, its money..). </p>\n\n\n\n<p>This doesn&#8217;t leave me with any firm conclusions beyond some possible routes to analysis. It seems likely that simple analysis based on static descriptions of community and the environment aren&#8217;t going to give us answers. We need to understand dynamics of groups opening up and enclosing over time, what sustains them, and what they might find valuable in exchange. We need agent based modelling of the network structures these occur over, and ways of translating from local structure in networks to more &#8216;bright-lined&#8217; social models of groups. We need to move beyond the simple &#8216;economic mathematics&#8217; that is often developed from the the club economics of Buchannan and Olson and to develop much more sophisticated and flexible models that allow the nature of exchange and goods to change when viewed from different perspectives.</p>\n\n\n\n<p>All in all it emphasises the conclusion I&#8217;d reached, that diversity is a first order principle. All forms of diversity and the more diverse the better, provided the coordination between groups is principled. There&#8217;s a lot to unpack in that word &#8216;principled&#8217; but I feel like its the link to the ethical dimension I&#8217;ve been missing. I need to dig deeper into notions of &#8216;care&#8217; (Moore, Priego) and &#8216;flourishing&#8217; (Holbrook) to tease this out. <br></p>",
68
+ "schema_version": "https://commonmeta.org/commonmeta_v1.0rc2.json"
69
69
  }
@@ -2,13 +2,12 @@
2
2
  "id": "https://doi.org/10.53731/r294649-6f79289-8cw16",
3
3
  "type": "BlogPost",
4
4
  "container": {
5
- "identifier": "2749-9952",
6
- "identifier_type": "ISSN",
7
5
  "type": "Blog",
8
6
  "title": "Front Matter",
7
+ "identifier": "2749-9952",
8
+ "identifier_type": "ISSN",
9
9
  "platform": "Ghost"
10
10
  },
11
- "content": "<p>A few weeks ago Kafkas et al. (2013) published a paper looking at current patterns of how datasets o biological databases are cited in research articles, based on an analysis of the full text Open Access articles available from Europe PMC. They identified data citations by:</p><ol><li>Accession numbers available in articles as publisher-supplied, structured content;</li><li>Accession numbers identified in articles by text mining;</li><li>References to articles from the ENA, UniProt and PDBe records.</li></ol><p>They could show that text mining doubles the number of structured annotations available in journal articles (from 2.26% to 5.15%), and that these structured annotations should be extended beyond the ENA, UniProt and PDB identifiers that their analysis focused on. ENA identifiers (for nucleotide sequences in GenBank, EMBL or DDBJ) make up the largest group, with 160,112 identifiers found in the 410,364 articles that were analyzed.</p><p>Another result in the paper is that references to articles in these databases show little overlap with database links found in articles. One of the conclusions drawn by the author is that</p><blockquote>Text-mining can be used to extend structured data citation, and could be a basis for the development of services to help authors or editors to add structured content at the beginning of the publication process, rather than after the fact.</blockquote><p>Adding structured data citations during the authoring phase of a manuscript requires tools that make this process easier, providing auto-linking and verification without requiring extra input from the author. Scholarly Markdown is an ideal platform for these tools, as it is easier to extend than traditional word processors such as Microsoft Word. During a small workshop around persistent identifiers for data (<a href=\"http://datacite.org/\">DataCite</a>), people (<a href=\"http://orcid.org/\">ORCID</a>) and geological samples (<a href=\"http://www.geosamples.org/igsnabout\">IGSN</a>) that took place yesterday and today at the <a href=\"http://www.gfz-potsdam.de/portal/gfz/cegit\">GFZ Potsdam</a> I worked on a tool that does auto-linking for these identifiers:</p><ul><li>IGSN. <a href=\"http://www.geosamples.org/igsnabout\">International Geosample Number</a></li><li>MGI identifiers for genetically modified mouse strains in the <a href=\"http://www.findmice.org/about\">Internal Mouse Strain Resource</a></li><li>ENA. <a href=\"http://www.ebi.ac.uk/ena/about/about\">Genbank / ENA / DDBJ nucleotide sequences</a></li><li>UniProt protein sequences from the <a href=\"http://www.uniprot.org/help/about\">UniProt database</a></li><li>PDB. <a href=\"http://www.rcsb.org/pdb/static.do?p=home/faq.html\">Protein Data Bank protein structure information</a></li></ul><p>The list includes the IGSN, the database identifiers studied by Kafkas et al (2013), and the MGI identifier for genetically altered mice. In the life sciences there is a long tradition - and requirement by journals - to use database identifiers for data, but identifiers for resources such as genetically modified mice are unfortunately not in common use.</p><p>This blog uses the Pandoc markdown processor and the Jekyll static website generator. The easiest way to implement this functionality was by writing a filter for the liquid templating engine used by Jekyll, and provide this filter as a Jekyll plugin. The Jekyll plugin can be found at <a href=\"https://github.com/mfenner/jekyll-scholmd\">mfenner/jekyll-scholmd</a>. The plugin expects the name of the identifier, followed by a colon and optional space, followed by the identifier:</p><pre><code>GenBank: M10090\nIGSN: JRH964436\nMGI: 96922\nUniProt: P02144\nPDB: 1mbn</code></pre><p>This input is automatically translated into <a href=\"http://www.ebi.ac.uk/ena/data/view/M10090\">GenBank:M10090</a>, <a href=\"http://hdl.handle.net/10273/JRH964436\">IGSN:JRH964436</a>, <a href=\"http://www.findmice.org/summary?gaccid/96922\">MGI:96922</a>, and information about the human myoglobin protein (<a href=\"http://www.uniprot.org/uniprot/P02144\">UniProt:P02144</a>, <a href=\"http://www.rcsb.org/pdb/explore/explore.do?structureId=1mbn\">PDB:1mbn</a>) is generated in a similar fashion.</p><p>The plugin was written in a few hours today, and is my first Jekyll plugin. There is room for improvement, e.g. support for more identifiers, better regex matching, validation of the resulting links, and automated tag generation if an identifier is found. Ideally the auto-linking should happen in the markdown and not the HTML output, so that these structured database links are also available in other markdown outputs such as PDF. But this is another example how Scholarly Markdown can make it easier for researchers to author documents without requiring a fancy web-based user interface.</p><h2 id=\"references\">References</h2><p>Kafkas, Ş., Kim, J.-H., &amp; McEntyre, J. R. (2013). Database Citation in Full Text Biomedical Articles. <em>PLoS ONE</em>. <a href=\"http://doi.org/10.1371/journal.pone.0063184\">doi:10.1371/journal.pone.0063184</a></p>",
12
11
  "contributors": [
13
12
  {
14
13
  "type": "Person",
@@ -18,9 +17,9 @@
18
17
  "family_name": "Fenner",
19
18
  "affiliations": [
20
19
  {
21
- "name": "Public Library of Science",
22
20
  "identifier": "https://ror.org/008zgvp64",
23
- "identifier_type": "ROR"
21
+ "identifier_type": "ROR",
22
+ "name": "Public Library of Science"
24
23
  }
25
24
  ]
26
25
  },
@@ -29,6 +28,7 @@
29
28
  ]
30
29
  }
31
30
  ],
31
+ "title": "Auto generating links to data and resources",
32
32
  "date_published": "2013-07-02T00:00:00Z",
33
33
  "date_updated": "2026-06-06T11:23:07Z",
34
34
  "description": "A few weeks ago Kafkas et al. (2013) published a paper looking at current patterns of how datasets o biological databases are cited in research articles, based on an analysis of the full text Open Access articles available from Europe PMC. They identified data citations by: 1. Accession numbers available in articles as publisher-supplied, structured content; 2. Accession numbers identified in articles by text mining;",
@@ -37,7 +37,12 @@
37
37
  "url": "https://storage.ghost.io/c/c5/33/c533c955-b5f3-4ff1-ae2d-6b52a212e602/content/images/2022/08/journal.pone.0063184.g003.png"
38
38
  }
39
39
  ],
40
- "image": "https://storage.ghost.io/c/c5/33/c533c955-b5f3-4ff1-ae2d-6b52a212e602/content/images/2022/08/journal.pone.0063184.g003.png",
40
+ "identifiers": [
41
+ {
42
+ "identifier": "https://doi.org/10.53731/r294649-6f79289-8cw16",
43
+ "identifier_type": "GUID"
44
+ }
45
+ ],
41
46
  "language": "en",
42
47
  "license": {
43
48
  "id": "CC-BY-4.0",
@@ -64,7 +69,6 @@
64
69
  "type": "IsPartOf"
65
70
  }
66
71
  ],
67
- "schema_version": "https://commonmeta.org/commonmeta_v1.0rc2.json",
68
72
  "subjects": [
69
73
  {
70
74
  "id": "https://openalex.org/subfields/1710",
@@ -74,7 +78,9 @@
74
78
  "subject": "Feature"
75
79
  }
76
80
  ],
77
- "title": "Auto generating links to data and resources",
78
- "url": "https://blog.front-matter.de/posts/auto-generating-links-to-data-and-resources",
79
- "version": "v1"
81
+ "url": "https://blog.front-matter.de/posts/auto-generating-links-to-data-and-resources/",
82
+ "version": "v1",
83
+ "content": "<p>A few weeks ago Kafkas et al. (2013) published a paper looking at current patterns of how datasets o biological databases are cited in research articles, based on an analysis of the full text Open Access articles available from Europe PMC. They identified data citations by:</p><ol><li>Accession numbers available in articles as publisher-supplied, structured content;</li><li>Accession numbers identified in articles by text mining;</li><li>References to articles from the ENA, UniProt and PDBe records.</li></ol><p>They could show that text mining doubles the number of structured annotations available in journal articles (from 2.26% to 5.15%), and that these structured annotations should be extended beyond the ENA, UniProt and PDB identifiers that their analysis focused on. ENA identifiers (for nucleotide sequences in GenBank, EMBL or DDBJ) make up the largest group, with 160,112 identifiers found in the 410,364 articles that were analyzed.</p><p>Another result in the paper is that references to articles in these databases show little overlap with database links found in articles. One of the conclusions drawn by the author is that</p><blockquote>Text-mining can be used to extend structured data citation, and could be a basis for the development of services to help authors or editors to add structured content at the beginning of the publication process, rather than after the fact.</blockquote><p>Adding structured data citations during the authoring phase of a manuscript requires tools that make this process easier, providing auto-linking and verification without requiring extra input from the author. Scholarly Markdown is an ideal platform for these tools, as it is easier to extend than traditional word processors such as Microsoft Word. During a small workshop around persistent identifiers for data (<a href=\"http://datacite.org/\">DataCite</a>), people (<a href=\"http://orcid.org/\">ORCID</a>) and geological samples (<a href=\"http://www.geosamples.org/igsnabout\">IGSN</a>) that took place yesterday and today at the <a href=\"http://www.gfz-potsdam.de/portal/gfz/cegit\">GFZ Potsdam</a> I worked on a tool that does auto-linking for these identifiers:</p><ul><li>IGSN. <a href=\"http://www.geosamples.org/igsnabout\">International Geosample Number</a></li><li>MGI identifiers for genetically modified mouse strains in the <a href=\"http://www.findmice.org/about\">Internal Mouse Strain Resource</a></li><li>ENA. <a href=\"http://www.ebi.ac.uk/ena/about/about\">Genbank / ENA / DDBJ nucleotide sequences</a></li><li>UniProt protein sequences from the <a href=\"http://www.uniprot.org/help/about\">UniProt database</a></li><li>PDB. <a href=\"http://www.rcsb.org/pdb/static.do?p=home/faq.html\">Protein Data Bank protein structure information</a></li></ul><p>The list includes the IGSN, the database identifiers studied by Kafkas et al (2013), and the MGI identifier for genetically altered mice. In the life sciences there is a long tradition - and requirement by journals - to use database identifiers for data, but identifiers for resources such as genetically modified mice are unfortunately not in common use.</p><p>This blog uses the Pandoc markdown processor and the Jekyll static website generator. The easiest way to implement this functionality was by writing a filter for the liquid templating engine used by Jekyll, and provide this filter as a Jekyll plugin. The Jekyll plugin can be found at <a href=\"https://github.com/mfenner/jekyll-scholmd\">mfenner/jekyll-scholmd</a>. The plugin expects the name of the identifier, followed by a colon and optional space, followed by the identifier:</p><pre><code>GenBank: M10090\nIGSN: JRH964436\nMGI: 96922\nUniProt: P02144\nPDB: 1mbn</code></pre><p>This input is automatically translated into <a href=\"http://www.ebi.ac.uk/ena/data/view/M10090\">GenBank:M10090</a>, <a href=\"http://hdl.handle.net/10273/JRH964436\">IGSN:JRH964436</a>, <a href=\"http://www.findmice.org/summary?gaccid/96922\">MGI:96922</a>, and information about the human myoglobin protein (<a href=\"http://www.uniprot.org/uniprot/P02144\">UniProt:P02144</a>, <a href=\"http://www.rcsb.org/pdb/explore/explore.do?structureId=1mbn\">PDB:1mbn</a>) is generated in a similar fashion.</p><p>The plugin was written in a few hours today, and is my first Jekyll plugin. There is room for improvement, e.g. support for more identifiers, better regex matching, validation of the resulting links, and automated tag generation if an identifier is found. Ideally the auto-linking should happen in the markdown and not the HTML output, so that these structured database links are also available in other markdown outputs such as PDF. But this is another example how Scholarly Markdown can make it easier for researchers to author documents without requiring a fancy web-based user interface.</p><h2 id=\"references\">References</h2><p>Kafkas, Ş., Kim, J.-H., &amp; McEntyre, J. R. (2013). Database Citation in Full Text Biomedical Articles. <em>PLoS ONE</em>. <a href=\"http://doi.org/10.1371/journal.pone.0063184\">doi:10.1371/journal.pone.0063184</a></p>",
84
+ "image": "https://storage.ghost.io/c/c5/33/c533c955-b5f3-4ff1-ae2d-6b52a212e602/content/images/2022/08/journal.pone.0063184.g003.png",
85
+ "schema_version": "https://commonmeta.org/commonmeta_v1.0rc2.json"
80
86
  }