{"id":252,"date":"2014-04-17T14:45:13","date_gmt":"2014-04-17T14:45:13","guid":{"rendered":"https:\/\/blogs-dev.lib.uconn.edu\/news\/?p=252"},"modified":"2014-04-17T14:45:13","modified_gmt":"2014-04-17T14:45:13","slug":"connect-preserve-share","status":"publish","type":"post","link":"https:\/\/blogs-dev.lib.uconn.edu\/news\/connect-preserve-share\/","title":{"rendered":"Connect. Preserve. Share."},"content":{"rendered":"<p>In the culture of the Internet, every organization needs to have a visual identity and a tag line. At the CTDA we are developing that visual identity a little at a time. Our first step was to create the minimalist wordmark that was our acronym. This minimalist approach was purposeful. The CTDA is meant to be a service and a resource that others use to preserve and make available their digital material. We wanted something that said who we were but didn&#8217;t require a lot of interpretation and did not compete with the content that the CTDA would deliver through the various presentation layers that would leverage CTDA content.<\/p>\n<div>\n<dl id=\"attachment_289\">\n<dt><a href=\"https:\/\/blogs-dev.lib.uconn.edu\/ctda\/files\/2014\/04\/CTDA_new.png\"><img loading=\"lazy\" decoding=\"async\" alt=\"The CTDA's new tagline\" src=\"https:\/\/blogs-dev.lib.uconn.edu\/ctda\/files\/2014\/04\/CTDA_new-300x176.png\" width=\"300\" height=\"176\" \/><\/a><\/dt>\n<dd>The CTDA&#8217;s new tagline<\/dd>\n<\/dl>\n<\/div>\n<p>As we began working with partners beyond our small implementation group, we found that of course no one knew what CTDA stood for, and in a world of silos and &#8220;complete solutions&#8221; people did not immediately understand what services we provided. \u00a0We are happy to explain that the CTDA is not a destination, but a service that organizations use to preserve their digital content and to make that content available to many presentation applications. The CTDA doesn&#8217;t itself own any content, rather it is a means of connecting organizations to preservation services so that they can share those resources with each other and the world.<\/p>\n<p>As this understanding became clearer in our own minds, we got to thinking about how to better express our new sense of the service in a sound bite. We decided that we would alter the wordmark and add a tagline that succinctly explained us. \u00a0Easier said than done. After much debate and discussion we chose the three words you see above: Connect. Preserve. Share. Our mission is to\u00a0<strong>Connect<\/strong>\u00a0participants to preservation services,. We\u00a0<strong>Preserve\u00a0<\/strong>digital content and metadata for the long term, and we make it possible to\u00a0<strong>Share\u00a0<\/strong>that content with each other, and with national aggregators like the DPLA.<\/p>\n<p>So there you go. I just took 300 words to say what we hope our tagline says in just three.<\/p>\n<p>Written by Greg Colati<br \/>\nReprinted from <a href=\"http:\/\/ctdigitalarchive.org\/\">http:\/\/ctdigitalarchive.org\/<\/a><\/p>\n<!-- AddThis Advanced Settings generic via filter on the_content --><!-- AddThis Share Buttons generic via filter on the_content -->","protected":false},"excerpt":{"rendered":"<p>In the culture of the Internet, every organization needs to have a visual identity and a tag line. At the CTDA we are developing that visual identity a little at a time. Our first step was to create the minimalist &hellip; <a href=\"https:\/\/blogs-dev.lib.uconn.edu\/news\/connect-preserve-share\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><!-- AddThis Advanced Settings generic via filter on get_the_excerpt --><!-- AddThis Share Buttons generic via filter on get_the_excerpt --><\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/posts\/252"}],"collection":[{"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/comments?post=252"}],"version-history":[{"count":2,"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/posts\/252\/revisions"}],"predecessor-version":[{"id":254,"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/posts\/252\/revisions\/254"}],"wp:attachment":[{"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/media?parent=252"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/categories?post=252"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs-dev.lib.uconn.edu\/news\/wp-json\/wp\/v2\/tags?post=252"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}