![\"Let's](\"https:\/\/juliehardesty.com\/notions\/wp-content\/uploads\/2015\/07\/38615433_1209cb0923_b.jpg\" "\\"Let's")
<\/a>biiiiig lick<\/a> by broterham<\/p><\/div>\n So you know those posts I wrote before where I was working on combined data sets from different sources that all have Solr indexes? That topic is – in trying to keep with the cooking\/baking\/food theme – on the back burner; I\u2019m letting the dough rise; it\u2019s in the fridge marinating; I\u2019m gonna get back to that.<\/p>\n The Rising<\/a> by scrambldmeggs<\/p><\/div>\n Other matters have come to the forefront of my metadata working life, such that I am now embroiled in concepts initially hard to grasp and tasks seemingly insurmountable. It can essentially be summed up in a few bullet points, though, I think:<\/p>\n I think that last point is the toughest, by far. This stuff becomes so esoteric and full of jargon so quickly. I also think that tends to happen when people don\u2019t quite understand what they are talking about themselves. Just keep reading and you’ll probably see for yourself what I mean.<\/p>\n Raisin cookie<\/a> by hanafan<\/p><\/div>\n I read a light-hearted blog called Go Fug Yourself<\/a> where publicity photos of celebrity fashion are examined for fabulousness and fugliness. The writing is entertaining\u00a0and no one is personally skewered but it\u2019s gotten to the point where they can\u2019t even talk about people wearing see-through clothing\/sheer fabrics anymore. They now talk about it using pizza as an analogy because it is so ubiquitous and terrible at the same time (the see-through clothing, not pizza). It can\u2019t really be discussed any further because it\u2019s been discussed ad nauseam and the writer\u2019s eyes, if not the reader\u2019s, glaze over (but are not see-through).<\/p>\n Krispy Kreme<\/a> by ableman<\/p><\/div>\n I think the same may apply when talking about\u00a0metadata sometimes. It effects everything and can still be the most difficult part of a project to understand and manage. Maybe it’s better\u00a0to talk in pure analogies that will keep the reader\u2019s attention than to try and directly discuss, say, the implications of MODS as expressed in RDF (because while complex hierarchical XML is expressible as complex sets of triple stores, it appears to be highly unusable in practical programmatic terms). For folks who read through that sentence without “blah-blah-blahing” in their heads, we have metadata nerdery in common. Yay us. But trying to express how this is relevant to developers, and to the systems they make, and to the end users who need to use those systems just can\u2019t happen when these issues mean different things to different metadata users and it\u2019s all so massively jumbled together with acronyms and metadata codespeak.<\/p>\n So I am endeavoring to address the\u00a0bullet points above, in article format and with more detail, using cases I know\u00a0and other cases I know about where these problems\u00a0are being tackled\u00a0in various ways. Whether this results in recommendations for ways to handle metadata transformations for different standards and uses\u00a0or is just an attempt to plainly explain the problems being encountered, it is going to be helpful to me and hopefully helpful to others as well. I would like a donut now, please.<\/p>\n","protected":false},"excerpt":{"rendered":" Hey blog, welcome to life – it happens. So you know those posts I wrote before where I was working on combined data sets from different sources that all have Solr indexes? That topic is – in trying to keep … Continue reading <\/a>\n
<\/a><\/a>