Month: August 2020
#ORCID profile – growing slowly + linked-data
Well, good news, I have added more content to my ORCID profile located here. In this case, my article, “Mind of ‘change’-Thinking: Exploring Henri Bergson, Time, Antifragility, and Life-Long Learning in Libraries,” published at Library Philosophy and Practice.
For those not familiar with ORCID, it is, “…a nonprofit organization helping create a world in which all who participate in research, scholarship and innovation are uniquely identified and connected to their contributions and affiliations, across disciplines, borders, and time.” What does this mean? Well, it basically is a non-profit that has built a system that is populated with growing dB of numeric identifiers for scholars who can use this ID to link all their work across the sprawling internet(z). 🙂
It just means that scholars in any field can attach their ORCID to publications so that the respective publishing platform produces a link to said scholar using a persistent identifier no matter what else that scholar produces.
In addition, ORCID is also a vocabulary that can be added to MARC-based authority cataloging, in a ‘preliminary’ (aka: test-pilot) fashion – looking like this: 024 #7 $a [insert identifier] $2 orcid. This tells the computer processing and linking authority data for persons and creators, that said authority name record, say, for ‘Jesse Lambertson,’ viewable here, is already in linked-data form, and contains information about ‘his’ ORCID profile. What this enables computers to do is make deliberate connections, across the internet, between the name as located in the Library of Congress Name Authority File (NAF) , ORCID, and publications that have ORCID attached (not too many at this point, but, Lord willing, should grow in the near future.
So, on the surface, is it simply an identifier. But it is also a tool that enables more snug relationships to be defined between creators and their works across the exponentially growing networked information universe.
thank you for reading
#Github #Code to the Arctic Vault
This is not anything important really, but I draw attention just because it reveals the flow of specific code-bases and attempts to archive said code (meaning, code deemed meaningful to a wide spectrum of users globally – or something like that).
I have been working on the Library Carpentry SQL curriculum code and language because I was recently on-boarded as a co-maintainer of the SQL curriculum. The co-maintainers had a sprint on Friday, August 14, 2020 – during which we threw a lot of time into closing issues and determining the nature of some of the work ahead of us. We closed almost half of the issues. This work then, as it updated the specific repositories in GitHub, then got included in the code being sent routinely to the GitHub Arctic Vault for archiving.
Again, not a big deal, but I was thus given a ‘badge’ for contributing to code that is being archived in that vault. I ONLY note this because it reveals the flow of code and intentions to keep around for the long term (thus the archive). I think this is pretty interesting to see the process ‘live.’
Thank you for reading
