Building an ICT-based Library - Workshop › documenti › repository › relazioni › ...ySource...
Transcript of Building an ICT-based Library - Workshop › documenti › repository › relazioni › ...ySource...
-
Source code provided vs Open Source vs Free softwareOpen Source comprises:
Access to the source code for the projectA license ‐ characteristically with:
RightsThe right to redistributeSource code providedDerive new system s from the software core
ResponsibilitiesMaintaining the integrity of the authors codeNo discriminationDistribution of the license with the code
-
Regional supportIssues of scalability (very large digital repositories)Issues of security (complex multi‐tier security requirements)Functionality – specific available in a particular productNot always an absolute choice:
Open source versions vs Supported versionsOpen source offered via a hosted service providerSupported open source
-
All public internet systems have potential vulnerabilities, including:
Cross‐site scriptingSQL injectionJavascript & other injection techniquesSpoofing of various sortshttp://www.webappsec.org/projects/statistics/
Open sourceCode may have vulnerabilitiesHowever: it is open to immediate inspection & correction
-
The platform for publicising the activity of your libraryGiving the library control over content presentationConsolidating all services in a single portal
-
Content Management is the “glue”Opportunities for patron community communication and engagement:
Web 2.0 Services: Wiki, TaggingNews, events, activitiesPortal functions
IFLA Website:Drupal
Canberra HospitalJoomla
-
Managing your institutional repository of assetsA workflow system to management asset submission in a distributed mannerAn archival management tool for long term management of the digital assets
-
Distributing the submission of digital assets across the organisationWorkflowConsolidating and preserving your assetsAsset managementAsset auditsIntegration with OPACDSPACEFEDORAGreenStone
-
Nice user front‐end & out‐of‐the‐box operationJava‐basedVery widely used – especially in UniversitiesGood workflow integration & search interfaceLimited web services layer interfaces (API’s)
-
New Zealand Digital Library ProjectWide installed base
Non‐university institutionshttp://www.greenstone.org/examples
Distributed in co‐operation with UNESCOGood cross‐platform installation capabilityNot as strong as Dspace in the built‐in end user workflow/submission
-
Flexible Extensible Digital Object and Repository ArchitectureJava‐basedCharacterised by a set of repository services and functionsA workflow & front‐end also need to be added (there are open source projects for this)Fedora has a better services‐level layer than Dspace/GreenstoneA “toolkit” or “architecture” rather than a “solution”
-
Internal institutional document repositoriesLarge scale document collections for internal useOverlap with digital libraryMultiple approaches:
Digital library software (as an intranet)Document management open source systemsWinIsys database software
http://www.intracen.org/tis/pub/impro/finalwinisis.pdf
-
Simplifying the complexity for your end usersClick‐through access to online database subscriptions
Making the client experience easier:Shibboleth EzProxy (not Open source/Freeware, but low cost)
-
A web‐based view into your collectionStandard functionality: OPAC, cataloguing, circulation, acquisitions, serials managementShould no longer be an “island” but a part of the “whole”Z39.50 for sharing resources with other parliamentary librariesWeb‐based OPACWeb 2.0 services
-
A rich choice of optionsEvergreenKohaPMBWinISYS‐basedGnuteca…. And others
Where to begin?
-
The workshop framework:Open Suse Linux (Virtualised)Apache, MySQL, PERL, Zebra: Koha
Workshop FocusMulti‐dimensional evaluation of Open Source
ArchitectureFunctionalityDatabase designCode designCommunity & Support
-
Copy an existing language set
Translate each of the pages •OPAC:52 pages •Staff client: 363 pages
-
MethodsHands‐on evaluation (download and install or online demo sites)Literature and community documentationPresentations about the software
-
A database schema evaluation will focus on several things:
Richness of the scheme – this is indicative of the functional depth of the systemTable normalisation – a series of steps to achieve a database design that allows efficient access in a relational database, minimising redundancy of dataManagement of bibliographic free‐text data
-
Language‐specific knowledge will yield greater insightsReview degree of code documentationReview object orientation or code reuseReview flexibility for multi‐lingual operation
-
Look for a roadmapLook at discussion groupsLook at code releases – major and minor
Eg http://git.koha.rogCrucial: look at organisations that can provide technical support for internal or cloud‐based hosting
-
Stable, well understood platform: Linux, Apache, MySQL, PerlTemplate‐based language configuration allows relatively simple extension to new languagesMore scalable with v3.0 ‐ the use of Zebra addresses some of the major deficits in scalabilityHave tested with collections > 600,000 items in size
-
Variable quality of codePartially 2 tier/3 tier design. Partial separation of code from form design with templates, but not MVC design
-
When implementing any system make sure you have good support arrangements: internally or commercially
-
Building the ICT LibraryService Definition, Service Plan, Needs assessmentTeam formation & governanceLaunching
Internal commitmentProfessional development
Sustainable support modelsRegional support serves? Hosted Services?Open source systems with strong communities/backing
Koha ... and DSpace
-
http://www.oss4lib.org/An online summary of open source systems relevant to libraries
http://www.librarytechnology.org/LibraryTechnologyReports.pl
Marshal Breeding’s yearly report for ALA
-
Dr Edmund BalnavesProsentient Systems Pty Ltd
72/330 Wattle St, Ultimo NSW 2007