North Carolina Digital Collections Collaboratory

from geekandpoke

I’m just in the midst of reading this ITHAKA S+R report on the sustainability of digital “projects.” It’s one of those reports where the basic ideas are so simple, but you didn’t realize that you knew them until you read it. Among the things that they suggest are vital to sustainability of projects:

• Dedicated and entrepreneurial leadership (this could also be ongoing leadership: how many digitization projects do you know of that fell apart or became static after the project manager left)?
• A clear value proposition (as in clear evidence of the value of the project)
• Minimizing direct costs (hello appropriate outsourcing!)
• Developing diverse revenue sources (of course that’s a dirty word in some parts of the academy)
• Clear accountability and metrics for success

Read more »

By Flickr user cdw9

I had the distinct pleasure of attending three RDA webinars in the last month and found them alternately informative, entertaining and frustrating. Here’s the lowdown:

Informative: The quality and knowledge of the speakers was great. Having a basic understanding of all of the concepts, I was not overwhelmed but got a greater view into some specifics of RDA that I was lacking. There has obviously been a lot of attention to RDA in the Tech Services world, but not as much in Digital Collections-y worlds, I guess because we probably don’t always deal as directly with the big thugs like MARC and AACR2. However, I’ve been wondering for a while now why more digital libraries (especially open-source and homegrown ones like ours) are doing more experiments with RDA, RDF, and especially linked data. Here at ECU we grab a lot of records from the catalog and cataloguers create the metadata in our MODS/METS records, so we are not immune to this change. I am really anxious for us to do something in this vein. The possibilities for broadening the use of our repository and for enriching it are just too good to ignore. Read more »

The State of North Carolina is redesigning its main website (www.nc.gov) and is seeking public input.   We want to hear from a wide range of people about what they want and need from the new site.  The goal is to build a site that makes it easier for everyone to obtain information about and perform transactions with NC state government.

Please consider taking a few minutes to answer a 9-question survey.  Feel free to share this survey through your social networks.

The survey closes at 5pm on Friday, November 5.

http://www.surveymonkey.com/s/ncgovwebdesign

Thank you for your time.

While recently developing a fairly involved Google Maps application, I quickly discovered that JavaScript libraries, such as jQuery, can only get you so far. None of them offered the level of specific mapping functionality I needed, and all the mapping plug-ins I looked at relied on the recently deprecated version 2 of the Google maps API. The only way to extend them was to rewrite large swathes of their code so they would work with the new API, which sort of defeats the purpose of using a plug-in for rapid development. I figured out what I needed via tutorials on Google’s website and several other sites, including “In usability we trust” maintained by Gabriel Svennerberg.

He’s written a series of tutorials on using the new Google Maps API, which he’s expanded into the recently published book: Beginning Google Maps API 3. All of the code demonstrated in the book is available for free download. I wish I’d had this book when I’d started the project – it would have saved a great deal of trial and error on my part. The author says that even those without much web development experience should be able to get a Google Map up and running. While I don’t disagree with this, the author introduces some advanced JavaScript fairly early in the book. Library staff members can follow the tried and true, copy and paste method, but some of the concepts, like anonymous and self-executing functions, might leave them scratching their heads a bit.

The author begins with a brief history of the Google Maps API and then takes a detour into upgrading from Version 2 of the API to Version 3, which the author recommends skipping if you don’t have any legacy applications to upgrade. However, I found it a useful general overview of the concepts discussed later in the book.

The rest of the book starts with the development of a very simple map. Then each chapter builds on the previous chapter in terms of map features and complexity; including such common mapping tasks as creating clickable markers that open information bubbles and creating polylines and polygons, used to create such things as driving directions, or to highlight specific geographical areas. The author follows the pattern of introducing a chapter’s main concepts and then working through them bit by bit, ending each chapter with the completed code for that chapter. I found this practice quite helpful as I didn’t have to flip back and forth as I have in other technical books to figure out the totality of what was going on.

The author also discusses several other often used features such as using Google’s
Geocoding service to find a user’s location as well as how to create custom markers. One particularly useful feature the author discusses deals with maps with large number of markers, anything above 1000, at which point a map’s performance starts to seriously degrade, particularly in Internet Explorer. This was something I ran up against very early in the development process. The author discusses the pro and cons of the various methods to deal with this problem, enabling a developer to easily choose the one that’s right for his or her particular application without having to code up each option and see what happens.

The book concludes with a very helpful overview of the API features discussed in the book, going over exactly how to use each class and method.

One concept I wish had been discussed in the book was dynamic sidebars, where a user can click a sidebar link to open the info window for a particular point. I found this one of the trickiest parts of developing our application.

All in all, I’d highly recommend Beginning Google Maps API 3 to those looking to develop Google Maps applications with the new API. It’s clearly written with lots of examples and pictures of exactly what the code’s output looks like. If you’re merely looking to embed the location of your library/institution in a Google Map this book is definitely overkill. However, if you plan on working on anything beyond the very basics this book is a definite plus. It will be particularly helpful to those with some previous JavaScript experience.

Image courtesy of Flickr user marttj

Image courtesy of Flickr user law_kevin

Question: Will the way volumes are digitized today change the way that work is done in the future: less close reading more broad reading/more data mining and deduction across corpora. Are the traditional monograph-driven disciplines a strong enough force against the tides of Google-ization (i.e. the “close enough” answer is the good enough answer)?
These questions are being explored by author David Weinberger in an upcoming book he’s working on called Too Big To Know and he gives some insight into his writing process and the arguments he is pulling together for his book on his Joho the Blog. It’s interesting both from the perspective of getting an inside look at an author’s process and for the sake of the arguments themselves. Check it out.

The State Library of North Carolina is pleased to announce its newest digital collection, Up & Out: Urban Development in North Carolina.

This report describes blight in Hamlet, NC.

This is the collection I hinted at way back in March (and yes, I’m as enthusiastic about these reports today as I was then).  I haven’t come up with any secrets regarding how to quickly and efficiently draw people to what’s inside; most of my ideas involve a lot of loving description, as I speculated months back. For now, I’m relying on a relatively straightforward web site and word of mouth.

We’re still in the process of scanning and uploading materials, but there’s plenty for people to explore at this point. We won’t get through scanning all of the printed reports as a part of this grant project, but should end up with at least 200-250 in the collection.

I’ve listed some complementary North Carolina collections and resources on the “More Resources” page, but if you know of and can recommend any others send them my way and I’ll make sure they get on the site.  As always, we’d love any feedback you might have.

Hi y’all. Allow me to introduce myself – I’m Kristy Dixon, and I recently (July 1) began my position as Digital Programs Archivist at UNC Charlotte. We’re pretty much starting from scratch, and we’ve got a clean slate, buckets of ideas, and a lot of excitement. I am SO stoked to be part of this North Carolina digital collections community. It’s excellent to have these wonderful examples of digital programs available as guidance and inspiration as we start out on this path. So first, thank you for being available for that!

We are exploring lots of options for digital asset management systems – right now, we are experimenting with a home-grown system, and while the backend seems ok so far, the interface needs major work. It’s clunky. The system also lacks capabilities for global find-and-replace, implementing controlled vocabularies, and easy data import/export. Also, folks with levels of expertise ranging from super-duper advanced to novice will be working on our projects, so we want to ensure some ease of use.

We’ve also been playing around with ContentDM, Omeka, and Fedora. There are aspects of all three that I really like and things that cause me some concern. (We’re excluding DSpace from the mix simply because it seems much more suitable for IRs and the like, but please feel free to correct me if I’m wrong about that and you love using DSpace for image-based collections.)

So I come to you, my digital library pals – I’m sure you have strong opinions on these products. Do you have songs of praise to sing about any of them? Any huge warnings about what NOT to go with? We want to make sure we get as many perspectives as we can so we choose the right system for our needs.

As of late this spring, the State Library and State Archives have merged efforts to provide a single point of access to our digital collections. We’re taking baby steps to do this, but as we move more collections online and the repository gets a much-needed facelift, we need to come up with a new name for this endeavor.

Here’s where we need your help (and I was able to work in reference to the term “crowdsourcing”).

We need a name that makes it clear that we aren’t NC ECHO, the Digital Heritage Center, or NC State (all of which either are in some way related to the State Library or State Archives or have the words “North Carolina” and “State”  in their name). The name should (a) make reference to the Archives & Library or (b) be completely neutral (and I think that we prefer a “neutral”  name as it allows our partnerships to grow, potentially).  We’ll be providing access to the historic and contemporary records and publications of state government (as we do now), and the name needs to reflect that (probably).  These materials can be as diverse as the Library’s 2003 document about prosecuting computer crimes from the Department of Crime Control and Public Safety to the Archives’s Black Mountain College publications and promotional photographs from the Department of Tourism. And, we’re both divisions within the Department of Cultural Resources, so there is some question as to whether we need to work a reference to that in?

Now, I realize that a name containing all of this information would be ridiculous, but I’m providing this information to give you some background.

OK. Let the crowdsourcing begin…

I knew that social media tools had really hit the mainstream when I got a flier encouraging me to become a fan of the Vacuum Cleaner Hospital on Facebook. That same day, I heard that the AFL-CIO was starting to use Twitter to reach out to new members. When operations as decidedly old-school as appliance repair shops and unions join the party, it’s pretty clear that we’re no longer in the realm of the young and hip. I’m just hoping that people weren’t citing the use of these tools by librarians to make the same point.

For those of you who are using social media to promote your digital collections (and I assume that’s most of you at this point), is it working? What do your web stats tell you — do you notice a bump in traffic after a well-timed post or tweet? Do you hear from people who find your stuff via Facebook who might not have run across it otherwise? I don’t know that anybody has questioned the rush to interactive tools by libraries, and I’m certainly not now, but I know that we all have to budget our time carefully and maintaining an active online presence does require time. Now that we’re a few years into it and have enough experience to step back and take a good look, what do you think: is it worth it?

There is now a printer/copier/scanner in the Special Collections department and Digital Collections has seen a dramatic drop in the number of “ad hoc” digitization requests that we do. These days we are pretty much only called in when the digitization is for publication purposes or when the format is unusual in some way (large, fragile, negatives, etc.). Most other scans are done on this multifunction device as pdfs.

On the one hand, this is good. We’ve completed a number of larger projects this year and our student workers can really focus on projects involving similar formats and workflows, increasing efficiency. However, now the tide has turned and several members of the Special Collections department are asking to have the pdfs “attached” to the finding aid (which, to us means, deposit it in the repository, create metadata, store for the long-term with the best methods possible…because the whole point is to organize all this digital ephemera not just have it “attached” to the finding aid).

So now I have the proverbial Angel on one shoulder and Devil on the other:

Angel: Access to something is better than nothing!
Devil: But pdfs of photographs and manuscripts? Ew.
A: They are perfectly readable online, i.e. access ready
D: But we don’t have a built in pdf viewer…yet…
A: We have asked, and gotten, identifiers, titles, and descriptions which is all we ask for to begin a digitization request anyway
D: But should we spend so much time on improving the metadata (which we will eventually do, if we follow the current workflow) of pdfs?
A: They are already just sitting around on servers, why not use them?
D: But if we deposit them, think of all the overhead involved? Would we be committing to digital preservation?
A: Aren’t you just being a snob?
D: No, I’m being a good steward of resources!

So I leave it to you, collaborators, what would you do?