How does your library exist in the Linked Data world? Is it a foaf:Organization, a schema:Organization, org:Organization, etc? Once you've decided that, what properties does your library have? For example, is it called by an rdfs:label, or skos:prefLabel, or dcterms:title, or something else entirely? These questions don't have a single correct answer, and therein lies the challenge of modeling data in RDF. Whether it's descriptive metadata, digital object relationships, or places, people, and things, you need to understand the options for mapping data and the pros and cons each mapping brings. This workshop will not be a presentation, but a collaboration: we are relying on attendees to provide concepts they've struggled to map in the Linked Data world. We would then go through the process of discussing as a group how to map those concepts and see if we can come to agreement as to the best approach(es). Ideally the end result of this workshop will be more uniform linked data and more standardized practices shared between organization. Because while one can map anything into RDF, the real challenge is doing it in a way that others outside of your institution will be able to make sense of.