[CODE4LIB] Why not Sharepoint?
Greetings list, I'm in the midst of establishing a corporate archive/RM program and soon will need to make a convincing case for why Sharepoint's Document Library/Search Centre is not a viable option for managing our archival digital objects and their associated descriptions. Does anyone have any personal experience using Sharepoint for archival purposes, or know of any articles/blogs discussing it's suitability (or lack thereof) for this type of work? I've always heard don't use Sharepoint but am having a hard time finding evidence that I can use to support my case for a 3rd party solution. Any help is much appreciated! Thanks, Ned [cid:image003.jpg@01CF9CEC.406E0240]http://www.mattamyhomes.com/ Ned Struthers Archives Manager T (905) 829-7828 C (647) 385-6337 ned.struth...@mattamycorp.commailto:ned.struth...@mattamycorp.com Corporate Office: 2360 Bristol Circle, Oakville, ON Canada L6H 6M5 CONFIDENTIALITY NOTICE: The information in and attached to this email is intended only for the use of the individual or organization to which it is addressed, and only for the intended purpose by that individual or organization. It may be confidential or legally privileged and the recipient is not entitled to publish or further disseminate such information without the express written consent of the sender. Any distribution, copying, disclosure or other use by anyone else or for any other purpose is prohibited and is not a waiver of privilege or confidentiality. If you have received this email in error, please notify the sender immediately. Thank you.
Re: [CODE4LIB] Why not Sharepoint?
Hi Ned, The biggest case for SP is boiled down to 2 things in my mind. 1) its terrible at preservation. If you are just using it as a digital asset mgmt system its fine, but if you need the preservation component go with something else. 2) SP is decent at doing everything, but is not good at any 1 thing. Its a jack of all trades, master of none. If you want to do 1 thing really well find something else. But, if you need something that does everything, its almost your only option. There are probably plenty of other arguments, but those 2 usually sum up SP in the discussions I have with people. Jacob Ratliff National Fire Protection Association Archivist/Taxonomy Librarian On Jul 11, 2014 6:41 AM, Ned Struthers ned.struth...@mattamycorp.com wrote: Greetings list, I'm in the midst of establishing a corporate archive/RM program and soon will need to make a convincing case for why Sharepoint's Document Library/Search Centre is not a viable option for managing our archival digital objects and their associated descriptions. Does anyone have any personal experience using Sharepoint for archival purposes, or know of any articles/blogs discussing it's suitability (or lack thereof) for this type of work? I've always heard don't use Sharepoint but am having a hard time finding evidence that I can use to support my case for a 3rd party solution. Any help is much appreciated! Thanks, Ned [cid:image003.jpg@01CF9CEC.406E0240]http://www.mattamyhomes.com/ Ned Struthers Archives Manager T (905) 829-7828 C (647) 385-6337 ned.struth...@mattamycorp.commailto:ned.struth...@mattamycorp.com Corporate Office: 2360 Bristol Circle, Oakville, ON Canada L6H 6M5 CONFIDENTIALITY NOTICE: The information in and attached to this email is intended only for the use of the individual or organization to which it is addressed, and only for the intended purpose by that individual or organization. It may be confidential or legally privileged and the recipient is not entitled to publish or further disseminate such information without the express written consent of the sender. Any distribution, copying, disclosure or other use by anyone else or for any other purpose is prohibited and is not a waiver of privilege or confidentiality. If you have received this email in error, please notify the sender immediately. Thank you.
Re: [CODE4LIB] Why not Sharepoint?
On Fri, Jul 11, 2014 at 10:10:40AM -0400, Jacob Ratliff wrote: Hi Ned, The biggest case for SP is boiled down to 2 things in my mind. 1) its terrible at preservation. If you are just using it as a digital asset mgmt system its fine, but if you need the preservation component go with something else. I've never used Sharepoint, but really it boils down to coming up with a list of requirements for a digital preservation storage system: - It must have an audit log of who did what to what when - It must do fixity checking of digital assets - At minimum, it must tell you when a fixity check fails - It really should be able to recover from fixity check failures when an object is read - Ideally it should discover these *before* an object is accessed, recover, and notify someone - It must support rich enough metadata for your objects - It must meet your preservation needs (N copies distributed over X distance within Y hours) - It must be scalable to handle anticipated future growth. I'm sure there are more, I haven't had much coffee yet this morning so I'm missing some. And honestly, you have to scale your requirements to what your specific needs are. *Only* then can you evaluate solutions. If you've got a list of requirements, you can then ask I need this. How well does SP (or any other possible solution) meet this need? -- Thomas L. Kula tlk...@columbia.edu Senior Systems Engineeer, Unix Systems Group Library Information Technology Office Columbia University in the City of New York
Re: [CODE4LIB] Why not Sharepoint?
On Jul 11, 2014, at 10:33 AM, Thomas Kula wrote: On Fri, Jul 11, 2014 at 10:10:40AM -0400, Jacob Ratliff wrote: Hi Ned, The biggest case for SP is boiled down to 2 things in my mind. 1) its terrible at preservation. If you are just using it as a digital asset mgmt system its fine, but if you need the preservation component go with something else. I've never used Sharepoint, but really it boils down to coming up with a list of requirements for a digital preservation storage system: - It must have an audit log of who did what to what when - It must do fixity checking of digital assets - At minimum, it must tell you when a fixity check fails - It really should be able to recover from fixity check failures when an object is read - Ideally it should discover these *before* an object is accessed, recover, and notify someone - It must support rich enough metadata for your objects - It must meet your preservation needs (N copies distributed over X distance within Y hours) - It must be scalable to handle anticipated future growth. I'm sure there are more, I haven't had much coffee yet this morning so I'm missing some. And honestly, you have to scale your requirements to what your specific needs are. *Only* then can you evaluate solutions. If you've got a list of requirements, you can then ask I need this. How well does SP (or any other possible solution) meet this need? So it doesn't look like you're just coming up with cases that Sharepoint doesn't do, you might consider something like the TRAC checklist: 2007 version, from CRL: http://www.crl.edu/sites/default/files/attachments/pages/trac_0.pdf 2011 update from CCSDS: http://public.ccsds.org/publications/archive/652x0m1.pdf The 2011 update should mirror what's in ISO 16363. Most of the other certifications that I've seen look more at the organization, and don't have specific portions for technology. -Joe ps. A quick search for 'SharePoint' and 'OAIS' led me to : http://www.eprints.org/events/or2011/hargood.pdf ... which as best I can tell is the abstract for a poster at OR2011.
