Skip to main content

The Basics: Large scale Digital Project Management Part 1

The Basics: Large scale Digital Project Management Part 1

I went through a class last year about digital project management, and as much as I was impressed at the technical part of the class, and the part of the class where we designed a website to put the digital stuff up, I was surprised to find out that the class had very little to do with large scale project (items that were over 100 items). It also completely ignored book digitization. This is odd, because 90% of my job is large scale digitization book efforts.

There are a few things that you need to consider when doing a large scale digitization effort (especially if it’s books).

What is the quantity of items to be digitized?

A collection of 200 items is going to be treated differently than a collection of 14,000 items.

How much variety is there in the group of items?

Are they all books? All pictures? Are they mixed documents? Are they bound? If you find that the group has many subgroups, go ahead and divide them out and make each format a different phase of the project. Formats that you don’t have equipment for currently, or items that are difficult can be put at the end.

Who wants the items digitized and why?

The answer to this question can greatly change how much effort you put into a project. If the project is just a passing idea from someone who isn’t invested in it, then they probably won’t care how long it takes to get up, or what the quality is.

When do they want the items to be through scanning?

If they expect a 14,000 item collection to be done in three months, this might be an indication that the person has unrealistic expectations. Then again, if they say they don’t care when it’s done, assume they mean a year or two.

When do they want the items returned?

Do they want the items returned all at once, or in batches? Just keep in mind that if they want the items returned all at once, that means you have to store the items somewhere. It’s easier to do things in batches, have them delivered and have them sent back.

When do they expect the items to be on-line and accessible?

Some people assume that after something is scanned, it’s immediately available on-line. Make sure they are aware that it may take twice as long to post process and item as it took to scan it.

Are there any copyright restrictions that need to be taken into consideration?

A digital collection is almost useless if you don’t have the rights to make it available on-line. Make sure that you know what restrictions are there, and how you can work with them to make sure the collection gets to the people they need to.

Do we have storage space for all the files for 10 years?

When you’re dealing with a book project, remember that each book has about 300 pages, and each page is an image. If you put them into a PDF, that helps on the size, but you still have the problem about storing the files for archival purposes. Do a few test documents and find out how much space you’ll need if every item in the collection was done the same way with the same specifications.

Do we have a content management system that can handle that many items?

A traditional website can only handle so many items. If you want a large scale digitization project to be useful, you might consider getting a content management system created for large collections that will support the correct metadata and searching.

Stay tuned for Part 2: Project planning

Comments

Popular posts from this blog

The Workload Iceberg for Digital Collections and Initiatives

In the last few weeks, I was asked to write a small paragraph explaining my area to others in the library.  I was happy to do this, as many people say they don’t know what my people do.  It’s sometimes hard to explain to others what we do without going into overtly technical topics and terms.  If we have done our job right, we’re practically invisible, which is the way it should be.  Anyway, writing the description made me realize why there is often a mis-match between what we do and what people think we do.  I’ll let you read the description yourself.  I’ve underlined the important bit. “Digital Resources is primarily an Open Access publisher.  We publish both born digital items (produced by students or faculty), and we scan to publish or republish old items. We curate digital collections through the whole digital life-cycle. Our work is a bit different from other departments because the more work we finish; the more work we create in having to maintain the collections. We’re no

Bureau of Indian Affairs- Digital Collection

The Bureau of Indian Affairs is one of the oldest Bureaus in the United States.  It was established in 1824 by Secretary of War John C. Calhoun . While the history of the organization has been controversial, their records are open to the public.  This collection brings together letters distributed from the Bureau of Indian Affairs starting in 1832 and going on into 1966. View the rest of the collection:  http://bit.ly/2h0hKvW 

Documentation and Good Management in Digital Libraries

This month is all about self-evaluations for me and my employees.  Because of this, I have been thinking about how a manager is supposed to show their work and their worth. The easy answer is to say that if the employees are doing well, then the supervisor is good. It could be that the employees are doing well despite a bad supervisor. An employee doing badly is also not a sign of a bad supervisor. So what tangible thing can I say makes me a good or bad supervisor? Throughout the year, I try to focus on the actions I take to make my employees' lives at work better. I try to give them direction, advice, and help make things easier. I also try to champion them. Things do not always work but I adjust. When I sit down to write my own evaluation, though, I end up writing about documentation. To me, that is a concrete indicator of a good supervisor. They care enough about the work, and their employees, to write things down and make a record. I want to challenge everyone to write