{"id":2307,"date":"2014-06-30T16:44:53","date_gmt":"2014-06-30T16:44:53","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=2307"},"modified":"2014-06-30T16:44:53","modified_gmt":"2014-06-30T16:44:53","slug":"week-five","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/metadata-standards\/week-five\/","title":{"rendered":"Week Five"},"content":{"rendered":"
This week my weekly goals included developing a standardized use case template and working with the github metadata directory page. I have never written or worked with use cases, so the first step in this process for me was to do my homework. I did some light reading to familiarize myself with use cases. Earlier in the Summer my mentor, Rebecca Koskela, sent me a use case template, which I familiarized myself with. We will be doing some revisions on this template in order to include additional fields.<\/p>\n
My GitHub time this week was spent making additional edits to the page. There were a few broken links in the use cases on the page as well as in the standards. One of the major issues with metadata standards (from a librarians perspective) is that standards are often being revised or improved or scrapped altogether. While it wasn’t a huge issue regarding the standards on the GitHub page, I did get to see how content can quietly go out-of-date.<\/p>\n
I will spend this next week continuing work on the GitHub page, as well as working with the use case template.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
This week my weekly goals included developing a standardized use case template and working with the github metadata directory page. I have never written or worked with use cases, so the first step in this process for me was to do my homework. I did some light reading to familiarize Continue reading Week Five<\/span>