Tuesday, September 23, 2014

Chapter 3 & 4 Reflection [Miller, S. J. (2011). Metadata for digital collections. Newyork: Neal-Schuman]



Metadata creation is part art and part science. The art is in how one uses language to create metadata to describe something, and the science is using the rules of a given metadata scheme. Some of the Dublin Core metadata recommendations are quite confusing. I found the coverage, relation, and source terms to be most troubling. I can see it will take practical experience to develop a better understanding of their application.
I could get lost in subject analysis. I enjoy this kind of thinking, and I do like doing the research subject analysis involves. It is troubling that others see this as a time sink. Nevertheless, I do understand one has to place limits on how much time to spend on solving the problem. Pragmatically there is a balance between subject analysis and tagging. Subject analysis will involve a controlled vocabulary but, what about tagging. Some user might be searching for a "red" boat in my collection of boats. I am curious how the content of an object is analyzed into a balanced granular set of terms that aid search and retrieval. I am not a big fan of putting my "red" boat in only the description field and relying on it being picked up in a query.
I envision one need what is akin to a style guide when creating and assigning metadata to something. Hard copy forms, or index cards with templates for a given metadata scheme could be helpful, and these are tools I would develop for my purposes when making a collection. Each item in the collection has a hard copy or digital template that is filled out before the record is built in the database. This allows one to audit the project before building it as well as facilitating the data entry phase when making the digital collection. Lastly, I can see how training and education in metadata is an important part of building digital collections. I would like to see certification programs developed for metadata.

Metadata Matters

I discovered this blog and thought I would repost it here.

http://managemetadata.com/blog/

Sunday, September 21, 2014

My Reflection on the One-to-One Principle and Metadata



Edward Steffen Morrow Jr.
Metadata for Digital Resources
Reading Reflection: Assignment 1
September 14, 2014

Reference to this Article
Miller, S. J., & 10th International Conference on Dublin Core and Metadata Applications, DC-2010. (December 01, 2010). The one-to-one principle: Challenges in current practice. Proceedings of the International Conference on Dublin Core and Metadata Applications, 150-164.
A couple of things come to mind after reading the Miller article. My thoughts (opinions) center on accepted wisdom of standards, competency, and required skills. I like the 1:1 principle. It fits with what I want to see on the Internet. I hold a strong opinion that each resource should be described as a single entity, and every resource should have its own description. Each item should have a separate metadata record. Of the example in the article, I like the options 1 (page 155) and 2 (page 155 – 156). However, these options are not gold standards in my opinion. I think they are appropriate substitutions and fit best with workflows. Despite their drawbacks, I see these options as good teaching example of how-to-create metadata to describe resources.
I see a better solution driven from the examples given in the article as well as from the comments of the author. In my opinion, the major stakeholders need to convene and come to an agreement on what are best practices for resource description. This agreement should take place via open source documentation and group collaboration governed by a working task force. The goal of this task force is to create a set of standards for resource description grounded in the 1:1 principle and submit this documentation to the National Standards Institute and the International Standards Organization. This documentation should include new necessities for OAI harvesting whereby the harvesting protocols flag ambiguous metadata for correction and clarification. The OAI harvesting protocols need fixing, so they do not allow ambiguous metadata into the record. The system should have a set of checks and balances that explicitly state and identify when the 1:1 principle is violated as well as identifying the ambiguous metadata.
I also believe that the time has come to require specific training in the 1:1 principle. This training should be at the bedrock of all metadata creation documentation. The 1:1 principle should be a gold standard that all software has to meet based on NSI and ISO certification requirements. In other words, new digital resource platform software should be rooted in the 1:1 principle. Stakeholders should only use software certified by the NSI or ISO that is 1:1 certified. Old software that does not meet the 1:1 principle needs to be phased out by a selected target date. My idea may seem like a radical approach. In my opinion, the future of the Internet depends on it for reasons of integrity, quality, and efficiency.
I also feel that the individuals charged with describing resources on the Internet should be required to have the appropriate training and or certification in the 1:1 principle. Consequently, resources identified in a fashion that does not follow the 1:1 principle should be explicitly identified as violating the standard so users can make better-informed judgments about the quality of the metadata.
I like how the book clarifies that metadata is a human construct with multiple components. In addition, I understand that metadata is a tool humankind uses to make sense of the information on the Internet. I also appreciate that metadata is a structured use of language and that metadata schemes exist to impart order to the chaos everyday language imparts when used for descriptive purposes. I do like Dublin Core, but it has many limitations when it used to describe resources with multiple manifestations. In this case, more than one manifestation. I like that Dublin Core offers customization options to create new elements. However, I found the creation of new elements made me really question and ponder how an item is described. My thoughts often delved into the metaphysical realm. I found myself drawing diagrams and bubble maps to put boundaries and connections between the words I wanted to use to describe a particular resource. The act of creating a metadata element with paired values is an art as well as a science in my opinion. It is an action where ignorance can produce unintended effects.
I feel metadata creation and its study is a worthwhile topic. It is a core component of digital resources and worth exploring. The Internet needs people who are skilled in the creation of quality metadata. I look forward to learning more about metadata and its application it to digital and analog resources.

Domain Name System High Level Review

As a class assignment I had to explore what the Domain Name System is and write up a small discussion about it on our class blog. This write up is not an in-depth review, it is simply a cursory overview.

The Domain Name System (DNS) is analogous to a telephone directory for the Internet. It translates domain names like www.google.com to a string of numbers called an Internet Protocol or IP address such as as 2607:f8b0:4001:c00::63 (Google’s IP address) and visa-versa. It is a critical component or infrastructure of the Internet. Almost all applications that operate on the Internet utilize the Domain Name System. It is also known as a translation system. It is a simple but sophisticated system. A single root server in 2012 was capable of handling up to 400 billion address translation or look-up requests per day. Every time an individual wishes to access a website, the Doman Name System is the primary tool used to complete that request. The Domain Name System is also a decentralized system. No single server of computer controls the system. The look-up table is spread across at least 13 root servers. The geo-spatial location of the servers is kept secret for security purposes. However we do know some information about the nature of the servers. They use a tree like hierarchy. The root server is unnamed. Below it are the top level servers. In 1998 seven top level domains were created:
.com - commercial
.org - organization
.net - network
.int - international organizations
.edu - U.S. higher education
.gov - U.S. national and state government
.mil - military
And one Infrastructure top level domain named .arpa.
Numerous 2 letter country codes are also created around this time.
The Domain Name System was design in 1983 by Paul Mockapetris. Prior to the DNS, Internet name spaces where resolved through a central location using a single table called HOST.TXT. As the Internet grew and the number of hosts expanded, the ability of the HOST.TXT table to do its job became strained. A new system was needed, and it had to be decentralized. It was too cumbersome and inefficient to rely on a single file that had to be continuously updated and transmitted to the various shareholders. So the DNS concept was born as a solution to the bottle neck HOST.TXT had become.
The DNS system is not perfect. The issues with the DNS fall into organizational, technical, integrity & security, structural, political, and governance issues. The future of the DNS is driven by the pressures from these issues. Some of the major changes to the DNS in the future include support for Chinese characters, Non-Latin Characters, enhanced Unicode support, the addition of new top level domains such as .xxx for the adult entertainment industry, total or partial conversion to the IPv6 standard, DNS fragmentation (alternative DNS), critical levels of third-party registrar corruption, changes to the Uniform Domain Name Resolution Dispute Policy, and increasing governmental influence. One recent change to the DNS is the decision of the United States to give up its role as the main overseerer of the DNS name space.

References used

Domain Name System. (2014, September 14). In Wikipedia, The Free Encyclopedia. Retrieved 21:52, September 17, 2014, from http://en.wikipedia.org/w/index.php?title=Domain_Name_System&oldid=625478761

List of Internet top-level domains. (2014, September 17). In Wikipedia, The Free Encyclopedia. Retrieved 21:53, September 17, 2014, from http://en.wikipedia.org/w/index.php?title=List_of_Internet_top-level_domains&oldid=625906913

Mockapetris, P. (1988-08-01). Development of the domain name system. Computer communication review, 18(4), 123-133. doi:10.1145/52325.52338

National Telecommunications and Information Administration (2014 14, March). NTIA Announces Intent to Transition Key Internet Domain Name Functions. Retrieved from http://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transition-key-internet-domain-name-functions

Pope, M., Warkentin, M., Mutchler, L. A., & Luo, X. (2012). The Domain Name System--Past, Present, and Future. Communications Of The Association For Information Systems, 30329-346.

Saturday, September 13, 2014

My Summer Internship Tumblr Post

I interned at the James K. Hosmer Special Collections library over the summer. I was required to create a Tumblr post documenting something about the experience.
Here is a link to my Tumblr post.Evey Picture Tells a Story
http://hclib.tumblr.com/post/97156690156/every-picture-has-a-story-to-tell-i-discovered-the

Friday, June 20, 2014

Pharmaceutical Microbiology: New antibiotic in development

Pharmaceutical Microbiology: New antibiotic in development: A new drug designed to treat tuberculosis could be the basis for a class of broad-spectrum drugs that act against various bacteria. Inte...

Tuesday, February 25, 2014