Hello,

I would definitely go open-source. However, a librarian needs to be willing to 
learn how to mitigate the issues that comes with it. I say go for it. This list 
is a great resource when you ruin into issues. I think file format is very 
important when arching archiving for preservation; do you just eat the content 
or are there intrinsic things that you want to capture. For pictures you want 
to at least be able to get good scanner that can give you at least 600pi. 

The image formats that you use matters alot. Pdf isn't always a good option for 
every thing. Some times plain test is a good solution. 

The problem with proprietary software is that your beholden to the limits set 
by the proprietor. With out much of a budget we should only be limited to of 
imagination and skill. The skills needed can be learned and will pay off for 
future projects. 

I think it is always good to get institutional support. Especially when at a 
college. I would write a proposal to the presidents office. Even if a large 
budget isn't necessary or possible. Institutional support from the top is huge. 

Thanks,

Cornel Darden Jr.  
MSLIS
Library Department Chair
South Suburban College
7087052945

"Our Mission is to Serve our Students and the Community through lifelong 
learning."

Sent from my iPhone

> On Oct 14, 2014, at 3:55 PM, P.G. <booksbyp...@gmail.com> wrote:
> 
> Hello,
> 
> Anyone has experience in digitizing archival materials? I need your
> recommendations/suggestions on how we can start with our digitization. We
> need to build a searchable website so the public can access our materials
> of images, publications and media files.
> 
> What platform did you use? Open-source or fee-base? What is your experience
> using it?
> 
> Basically, we started using Sharepoint but at this point, I believe it is
> only good for sharing of internal documents. We are on a limited budget so
> we may need to host it on our own server as well.
> 
> Any feedback or persons to contact for more info is highly appreciated.
> Thanks.
> 
> Chris

Reply via email to