{"id":75,"date":"2015-08-27T14:35:26","date_gmt":"2015-08-27T14:35:26","guid":{"rendered":"http:\/\/resources.culturalheritage.org\/comment\/?page_id=75"},"modified":"2015-08-28T13:29:16","modified_gmt":"2015-08-28T13:29:16","slug":"addendum-conservation-online-cool","status":"publish","type":"page","link":"https:\/\/resources.culturalheritage.org\/comment\/charting-the-digital-landscape-of-the-conservation-profession\/addendum-conservation-online-cool\/","title":{"rendered":"Addendum:\u00a0 Conservation OnLine (CoOL)"},"content":{"rendered":"<p><em>CoOL was not a focus of this project, but the future of CoOL was a topic that arose in all project conversations. Its outdated interface and high maintenance costs puts this resource at risk, and project participants spoke often about ways it might become a revitalized, sustainable resource. These discussions, filtered through the lens of the project team and advisory committee, offer useful insights into how CoOL might be restructured for the future. A possible pathway forward is addressed in this addendum.<\/em><\/p>\n<p>CoOL has long been the premier resource for online access to the literature of the field and an important communication channel for conservation professionals. It is, as one conservator noted, \u201cthe place you go to first for quick answers.\u201d Begun in 1987 by Walter Henry, then Lead Analyst in the Preservation Department at Stanford University Libraries, the resource consists of two related but distinct components: a listserv (\u201cConsDistList\u201d) and a portal of historic resources\/publications that cover a variety of conservation and preservation issues.<\/p>\n<p>CoOL has grown exponentially since its inception, and continues to be heavily used. In 2014, the resource had more than one million page views and 500,000 users. Given its longevity and heavy usage, it is not surprising that CoOL is showing its age. The interface and underlying code are outdated, and hosting and maintenance are costly.[1] Its search results are inconsistent and its embedded links are often broken. It cannot integrate the media-rich formats that have become a ubiquitous component of online resources. Some of CoOL\u2019s problems (e.g., broken links) have been addressed with individual fixes, but these have built up over time and make CoOL unwieldy to administer. Its value is diminishing, and it risks obsolescence without significant improvements in functionality.<\/p>\n<p>Conservation professionals have tolerated CoOL\u2019s problems because it remains a vital resource for the field. Its extensive content is vetted and edited by those in the profession, lending it an imprimatur that is valued in the community. CoOL also serves a little-acknowledged but highly important preservation function: by keeping resources in the portal for the long-term, CoOL ensures that they stay online even if their source sites should disappear. For these reasons, CoOL continues to be cited as the model of a trusted online resource in the profession. Indeed, when conservation professionals were asked about online resources over the course of this project, their response was often \u201cwe need something like CoOL, but better.\u201d<\/p>\n<p>The thousands of valuable, curated resources in CoOL argue for its redesign rather than the creation of a new resource. But any redesign that takes place must address CoOL\u2019s listserv and portal components independently. Each of these components has separate purposes, issues and needs.<\/p>\n<p><em>Conservation DistList (\u201cConsDistList\u201d)<\/em>[2]<br \/>\n<a href=\"#_ftn2\" name=\"_ftnref2\"><\/a>The listserv has approximately 10,000 subscribers from more than 90 countries. Information distributed via the list includes job and event postings, and inquiries about topics important to the field that range from the durability of archival boxes to environmental monitoring techniques. Messages sent to the list are vetted by a moderator and emailed to subscribers in the form of a weekly digest.<\/p>\n<p>The listserv provides a low barrier to entry for its subscribers, but it does not scale well when message throughput is high. The weekly digest message makes for an awkward reading format. Responses and discussion threads are not possible. Unlike most listservs, the administrative overhead for the ConsDistList is high because of its curated nature. There is a searchable archive of messages going back to the listserv\u2019s beginnings, but the search capability is not reliable, and searching is not optimized for broader discoverability on the open Web with search engines such as Google or Bing.[3]<\/p>\n<p>The limitations of the listserv format are particularly apparent when compared with newer, alternative forms of online communication such as forums or \u201cgroups.\u201d These platforms are easy to organize and search, can be accessed on the Web, allow threaded conversations that can be grouped by topic, and give users a choice about what they want to see and how they might wish to respond. For some organizations, discussion forums have superseded listservs as a community communication vehicle because of these more advanced features.<\/p>\n<p>Other organizations are using popular social media platforms, such as LinkedIn, Twitter, and Facebook, in lieu of listservs. However, a more \u201cideal\u201d platform for the conservation community might be one that offers the interactivity and topical organization of forums, coupled with capabilities that link topic threads to relevant resources on the Web. This functionality can now be found in popular commercial products,[4] and might filter down into more open products over time.<\/p>\n<p>There is a growing consensus that the ConsDistList needs to migrate to a more feature-rich platform for communication and archiving of the list\u2019s content. Newer and better alternatives to listservs are freely available, and moving to one of these platforms will facilitate timely discourse among colleagues and help build a knowledge base from the collective input of conservation professionals.<\/p>\n<p><em>The CoOL Portal<br \/>\n<\/em>The CoOL portal contains a wealth of information resources, including the listservs of more than 30 allied organizations and groups; a directory of conservation professionals; publications, professional papers, documents and links to online resources on 21 conservation topics; and the websites of allied organizations and specialty groups (as well as mirrored sites of several other organizations.) Most of the resources are formatted in HTML files that are pulled together, organized, and delivered by means of a complicated backend process that includes programming scripts and other specialized coding. This process, which has become unwieldy to administer, requires a new approach if CoOL is to become a more functional and sustainable resource.<\/p>\n<p>Deciding on this approach has been the subject of many discussions. While conservation professionals would like an overhaul that fixes all of CoOL\u2019s problems, this approach would be premature. There is uncertainty about <em>how<\/em> CoOL is used and what additional functionality is needed. Rather than pursue a \u201cbig fix,\u201d a more judicious approach would be to identify incremental improvements that would improve CoOL <em>and<\/em> yield information useful to building the resource in a more strategic manner.<\/p>\n<p>For example, converting CoOL\u2019s HTML-formatted resources into a wiki format would be a marginal improvement that yields substantial results. Each HTML page in CoOL would be standardized and properly indexed, so searching would improve. FAIC would be able to identify successful and unsuccessful queries, and could use its page analytics to see <em>what<\/em> is being searched. Both users and FAIC would see immediate returns, with FAIC gaining the information it needs to make informed decisions about further improvements.<\/p>\n<p>Before this approach can get underway, the number of HTML pages in CoOL needs to be determined, and a decision must be made about what portion of these pages should be targeted in an initial conversion. FAIC then could solicit bids to identify estimated conversion costs, and seek one-time funding to implement the conversion. While the conversion is taking place, FAIC could set up a workflow for capturing and reviewing search query successes and examining other information derived from page analytics. After a set amount of time, this information could be analyzed to determine how to move CoOL forward in a step-wise progression.<\/p>\n<p>The test-bed conversion of HTML records outlined above is one possible project that FAIC might pursue as it moves the portal portion of CoOL toward greater functionality. Other discrete elements in CoOL\u2019s dataset might prove equally feasible as test-bed projects. The CoOL Working Group, which sits within FAIC\u2019s administrative umbrella, is the logical entity to make these determinations and oversee work in this area. But before it can do so, the Working Group needs to expand its membership to include outside experts who can bring more technical knowledge to the process, and knowledge about business models for online resource (see below).<\/p>\n<p><em>A New Business Model<br \/>\n<\/em>Incremental projects such as the one proposed above will improve CoOL\u2019s functionality but they will not ensure its sustainability. A new business plan is needed to keep the resource alive into the future. At the moment CoOL is freely available, but it is not without cost. Since 2008 FAIC has assumed the burden of this cost, bolstered in part with modest individual donations. FAIC\u2019s backing keeps CoOL online and available, but cannot support anything other than minor improvements. Without a new business model, CoOL will continue to be at risk, even if new features and functionality improve the resource.<\/p>\n<p>Resource support comes in the following guises: subscription-based, member-based, and institutional sponsor-based models, or some combination thereof. Going forward, FAIC faces a quandary as it migrates CoOL from its current sponsor-based model: any new model that is fee-based will not succeed until improvements in CoOL are substantial enough to warrant such a fee.<\/p>\n<p>There are ways to implement a new model while improvements in CoOL are underway. For example, FAIC could ask for volunteers to help edit CoOL in return for free access to the resource if it became fee-based. Bridge funding might be available to cover costs associated with incremental and well-defined improvements (such as the wiki conversion project noted above), if a long-term support model can be convincingly articulated to a funder. In the end, FAIC in conjunction with the CoOL Working Group, needs to explore all funding models and move forward on a plan to implement a new business model in tandem with the development of CoOL.<\/p>\n<blockquote><p>What is this resource really worth to you? There are costs in bringing these resources together. Community tools have to be supported by the community. If we don\u2019t pay, it goes away.<br \/>\n-David Bloom, VertNet Coordinator, University of California, Berkeley<br \/>\nSpeaker, Digital Landscape Forum #1, San Francisco, 2014<\/p><\/blockquote>\n<p><u>Summary of Recommendations for CoOL:<\/u><\/p>\n<ol>\n<li>Identify and migrate the ConsDistList portion of CoOL to a more user friendly, functional communication platform.<\/li>\n<li>Conduct an assessment of CoOL\u2019s format and content, with an eye toward identifying and implementing a small project that will yield maximum impact on use of the resource, and give FAIC insights into the use of CoOL.<\/li>\n<li>Use this first project\u2019s results to identify and define the next logical project, and develop subsequent projects that build on each other in the same iterative manner.<\/li>\n<li>Identify a new business model that will help sustain CoOL in the future. FAIC must take the lead in making this decision, as it is CoOL\u2019s sponsor and administrative home.<\/li>\n<li>Expand the CoOL Working Group to include outside experts who can advise on technical aspects of conversion, agile project development, and business models for community-based resources.<\/li>\n<\/ol>\n<hr \/>\n<p><small>[1] In 2015, CoOL\u2019s costs will total approximately $80,000.<\/small><\/p>\n<p><small>[2] See <em>Conservation DistList Archives<\/em>. <a href=\"http:\/\/cool.conservation-us.org\/byform\/mailing-lists\/cdl\/\">http:\/\/cool.conservation-us.org\/byform\/mailing-lists\/cdl\/<\/a>. <\/small><\/p>\n<p><small>[3] This situation is even more problematic for the AIC Specialty Group discussion lists. These online lists use the same listserv software (Mailman) as the ConsDistList and are archived within CoOL, but they are closed lists that can be searched only by date and author.<\/small><\/p>\n<p><small>[4] Sinkov, Andrew. \u201cContext: Your Work Enriched by the Smartest Minds<em>\u201d. Evernote News<\/em>. October 2, 2014. <a href=\"https:\/\/blog.evernote.com\/blog\/2014\/10\/02\/context-work-enriched-smartest-minds\/\">https:\/\/blog.evernote.com\/blog\/2014\/10\/02\/context-work-enriched-smartest-minds\/<\/a>.<\/small><\/p>\n","protected":false},"excerpt":{"rendered":"<p>CoOL was not a focus of this project, but the future of CoOL was a topic that arose in all project conversations. Its outdated interface and high maintenance costs puts this resource at risk, and project participants spoke often about ways it might become a revitalized, sustainable resource. These discussions, filtered through the lens of [&hellip;]<\/p>\n","protected":false},"author":18,"featured_media":0,"parent":11,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-75","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/resources.culturalheritage.org\/comment\/wp-json\/wp\/v2\/pages\/75","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/resources.culturalheritage.org\/comment\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/resources.culturalheritage.org\/comment\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/resources.culturalheritage.org\/comment\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/resources.culturalheritage.org\/comment\/wp-json\/wp\/v2\/comments?post=75"}],"version-history":[{"count":0,"href":"https:\/\/resources.culturalheritage.org\/comment\/wp-json\/wp\/v2\/pages\/75\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/resources.culturalheritage.org\/comment\/wp-json\/wp\/v2\/pages\/11"}],"wp:attachment":[{"href":"https:\/\/resources.culturalheritage.org\/comment\/wp-json\/wp\/v2\/media?parent=75"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}