Chapter 12 Comparative Analysis of Software...

Chapter 12

Comparative Analysis of SoftwareEvaluation

Introduction

The evaluation of selected candidate software was carried out on different evaluation cri-

teria. This chapter deals with the comparative analysis of each software against the set of

evaluation criteria under broad and narrow subject categories.

Though the objective of the present study is to not compare one software with another

and decide the best among all, it is necessary to understand what are the general features

supported by each software under broad and narrow subject categories and will help users

to glance through different features in a tabular form. Thisanalysis may be helpful to

the Library Staff to know which area is more important and which software can be chosen

with a given set of environment. In the further sections of this chapter all the narrow criteria

which are defined for evaluation of OSS-DL are compared as a comparative table under the

broad subject categories.

12.1 Content Acquisition

Table 12.1 lists out all content acquisition related criteria in a tabular form. It is found

that all selected software support to upload digital documents through Web User Interface

except Fedora and Greenstone. Fedora & Greenstone has separate Librarian’s Interface

360

CHAPTER 12. COMPARATIVE ANALYSIS 361

through which documents can be uploaded into the repository. Duplicate checking of doc-

uments is supported only by EPrints and Greenstone. No othersoftware support duplicate

checking. One of the important feature of CDS-Invenio is it has capability to create bibli-

ographic database as well as has capability to manage digital documents.

EPrints and Fedora has unique capability to upload digital documents from existing URL.

Greenstone software also has this feature but this feature does not work properly with

Greenstone. Importing is handled by all software and all software support to import data if

it is available in XML format. All software have capability to export data into either XML,

DC format, METS, MARC format. Automatic extraction of keywords is at present handled

by only CDS-Invenio. No other software support to extract keywords from metadata or full

texts uploaded into the repository. CDS-Invenio, DoKS & Fedora supports to add different

versions of digital documents which is one of the important feature of digital library. Weed

out policy is at present supported by CDS-Invenio, DSpace, EPrints, Fedora & SOPS.

12.2 Content Management

Table 12.2 lists all evaluation criteria related to contentmanagement. CDS-Inveion &

DSpace software provide a good workflow management. CDS-Invenio can handle com-

plex workflow processess. EPrints, MyCoRe software to some extent provide workflow

management. DoKS and SOPS allow to create only submitters but does not support any

other work flow management such as creating reviewers, metadata reviwers, etc. Fedora &

Greenstone does not have any work flow management. Generating authority files is sup-

ported at present only by DSpace, DoKS, Greenstone & MyCoRe.DSpace & CDS-Invenio

has capabilities to show strength of each collection on web site.

12.3 Metadata Submission and Support

Table 12.3 lists all evaluation criteria related to metadata submission & support in a tabular

form. All the software have capability to upload descriptive, administrative & structural

metadata except SOPS. All software support UTF-8 hence it ispossible to add metadata

in any language. All software have capability to support Dublin Core metadata schema

except SOPS. CDS-Inveion, EPrints, Fedora & Greenstone supports to add metadata other

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

62

Table 12.1: Content Acquisition

CDS-Invenio DSpace DoKS EPrints Fedora Greenstone MyCoRe SOPS

Software sup-ports to allowto add biblio-graphic dataof books, re-ports, journalsas well as allother types ofdigital mediasuch as text,audio, video,image, dataset files etc.which is oneof the uniquefeature ofCDS-Invenio.

DSpace sup-ports to allowto add all typesof digital docu-ments rangingfrom books,reports, journalarticles, lecturenotes, tech-nical reports,thesis, images,audio/videofiles to datasets.

DoKS supportsto speciallyadd electronicthesis of a stu-dent as well asit supports toadd CurriculumVitae, workexperience,referenceinformation,annotationdetails, Edu-cation etc. ofevery studentalong withthe electronicthesis.

EPrints sup-ports to addarticles, booksections,monographs,conferenceor workshopitems, books,thesis, patent,artefact,show/exhibition,composition,performance,image, video,audio, dataset,experiment,teaching re-source.

Fedora sup-ports to uploadconventionaldigital ob-jects (such asbooks, othertext docu-ments, learn-ing objects,geospatialdata, im-ages, maps,computerprograms),Complex,Compoundas well asdynamic ob-jects (suchas videos,numerical datasets, their as-sociated codebooks andaudios as well.

Greenstonesupportsto add anytype of doc-uments suchas from books,reports, jour-nal/newspaperarticles, lecturenotes, tech-nical reports,thesis, images,audio/video,visual artfiles as wellas any otherdocuments.

MyCoRe sup-ports to addvariety of doc-ument suchas article,abstract, bibli-ography, book,dataset, pro-gram, thesis,examination,journal, learn-ing material,manual, mu-sic, notes,person infor-mation, picture,preprint, pre-sentation,research pa-per, service,statistical data,video etc.

SOPS sup-ports to addonly electronicpublicationssuch as pa-pers, keynotepapers, shortpapers, ab-stracts, postersetc.

CDS-Invenioallow to de-fine the do-main/scope ofthe digital li-brary for whomit is intendedfor.

DSpace isdesigned forcreating insti-tutional repos-itory of anyorganization.

DoKS is spe-cially meantfor organisingelectronic the-sis/dissertationsfrom any uni-versity.

Software hascapability todefine thedomain of thedigital library.

Fedora doesnot supportto define do-main/scopeof the digitallibrary.

Greenstonehas capabilityto define do-main/scope ofdigital libraryfor whom it isintended for.

MyCoRe hasbeen espe-cially designedfor creatinginstitutionalcontent reposi-tory or archivalsolutions.

SOPS is spe-cially meantfor organis-ing electronicpublications.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

63


CDS-Inveniocan be usedto organiseany type ofdigital docu-ments and itis designedfor all types oflibraries.

Software is in-tended for thefaculty mem-bers of anyorganization.

DoKS is in-tended foruniversitystudents for or-ganising theirthesis and theirCV’s online.

EPrints is basi-cally intendedfor creatingpreprint/postprintarchives butthe currentversion sup-ports addingother types ofdocuments aswell such asaudio/videocollections.

Fedora doesnot supportto define do-main/scopeof the digitallibrary.

Software isintended tocreate digi-tal library ofany type ofdocuments.

MyCoRe isdesignedfor authors,editors, read-ers where itsupports todefine differ-ent workflowfor differentgroups andallow endusers to uploaddocumentsdirectly.

It is intendedfor use of con-ference organ-isers and or-ganising elec-tronic publica-tions.

Software hasthe ability toaccept doc-uments inall desiredformats. Doc-uments canconsist ofmultiple files.Software givesthe ability tosubmit a docu-ment with morethan one file.

DSpace bydefault sup-ports to uploadPDF, AIFF, au-dio/basic, BMP,CSS, FMP3,GIF, HTML,image/png,JPEG, La-tex, MARC,Mahematica,Microsoft Ex-cel, Microsoftpowerpoint,MicrosoftProject, Mi-crosoft visio,Microsoft word,etc.

DoKS supportsto add any typeof file formatswhich are ofMIME type.It allow endusers to defineany MIME typeformats andcan uploadany MIMEtype documentformats.

All text for-mats are bydefault sup-ported by thesoftware, butsoftware alsosupports toupload JPEG,PNG, GIF,BMP, TIF fileformats, AdobePostscript,Adobe PDF,HTML file for-mats, MP3,AVI, MPEGfile formats.Software alsosupports to up-load MicrosoftPower Pint andWord formats.

Fedora sup-ports to uploadthe followingMIME typesof file for-mats: text/xml,text/plain,text/html,text/html+xml,text/svg+xml,text/rft, im-age/jpeg,image/jg2,image/gif,image/bmp,image/png,image/tiff,audio/mpeg,audio/x-aiff,audio/x-wavetc.

Greenstonesupports toupload severaltypes of digitaldocumentsand supportedplugins areavailable inGreenstonesuch as zip,gap, text, html,text, pdf, rff,word, ps, im-age, isis, nul,metadata xml,mp3, opendocument,lom, bibtextetc.

MyCoRe sup-ports to uploadall types of fileformats. Bydefault sys-tem supportscollections,dataset, event,image, ser-vice, software,sound, text,unknown,video, etc.

Though SOPSis meant foradding onlyelectronic pub-lications it alsosupports toupload otherfile formats.

Software doesnot carryout duplicatechecking whileuploading thedocuments intothe repository.

Software doesnot carryout duplicatechecking whileuploading thedocuments intothe repository.

Software doesnot carry outduplicationchecking whileuploading thedocuments intothe repository.

EPrints carryout duplicatechecking onthe basis ofTitle.

Fedora carryout duplicatechecking viaits PID numberi.e. PersistentIdentificationNumber.

Greenstonesupports tocarry out dupli-cate checkingwhile upload-ing the data.

MyCoRe doesnot carryout duplicatechecking.

SOPS does notcarry out dupli-cate checking.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

64


CDS-Inveniosupports toupload digitalobjects in nor-mal formats aswell as com-pressed digitalformats suchas zip, tgz, gz,gzip etc.

DSpace sup-ports to uploaddigital objectswith normalsize as well ascompresseddigital objects.

DoKS supportsto upload digi-tal objects withnormal size aswell as com-pressed digitalformats.

EPrints sup-ports to uploadnormal digitalobjects as wellas it supportsto upload filesending with.zip and .tar.gz.

Fedora sup-ports to uploaddigital objectswith normalsize as well ascompresseddigital filessuch as zip,tar, gz, gtar,gzip.

Greenstonesupports toupload digitalobjects withnormal size aswell as com-pressed digitalfile formatssuch as zip,tar, gz, gzipetc.

MyCoRe sup-ports to uploaddigital objectswith normalsize as well ascompressedfile formats.

SOPS sup-ports to uploaddigital objectswith normalsize as well ascompressedfile formats.

Software doesnot support toupload digitalobjects fromexisting URL.

Software doesnot support toupload digitalobjects fromexisting URL.

Software doesnot support toupload digitalojbects fromexisisting URL.

EPrints sup-ports to uploaddigital objectsfrom existingURL.

Fedora sup-ports to uploaddigital docu-ments fromexisting URLas well as itcan redirectto existingURL insteadof actuallydownloadingcontents intothe repository.

Greenstonehas the fea-ture to uploaddigital docu-ments fromexisting URLbut this featureis not workingproperly.

MyCoRe doesnot support up-loading digitalobjects fromexisting URL.

SOPS doesnot support up-loading digitalobjects fromexisting URL.

CDS-Inveniosupports dis-tributed/ com-munity basedacquisition.

DSpace sup-ports dis-tributed/communitybased acquisi-tion.

DoKS supportsdistributed/communitybased acquisi-tion.

EPrints sup-ports dis-tributed/communitybased acquisi-tion.

Fedora doesnot supportdistributed/communitybased acquisi-tion.

ThoughGreeenstonesupports dis-tributed basedacquisitionthis featuredoes not workproperly.

Softwaresupportsdistributedacquisition.

SOPS sup-ports dis-tributed/ com-munity basedacquisition.

CDS-Inveniosupports meta-data/contentimport. Thedata has tobe in MARCXML to MARC 21 or DublinCore format.The metadataand full textshave to beseparatelyimported.

DSpace sup-ports con-tent/metadataimport. Thedata has to bein the DublinCore format.

DoKS sup-ports to importmetadata ifit is availableXML format.DoKS supports to importall folders,users, filefor-mats, scrips,and recordscreated inDoKS.

Software sup-ports to importmetadata ofitems via DOII(via CrossRef),XML, PubMEDID, PubMEDXML formats.

Fedora sup-ports import ofdigital objectsif data is avail-able in XMLformat.

Greenstonesupports im-port of digitalobjects if datais available inXML format.

MyCoRe sup-ports to importdata and datahas to be in theXML format.

SOPS sup-ports to importdata if it isavailable inCSV file formatsuch as Excelor Access.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

65


Software sup-ports importingof bulk meta-data/content ofdigital objects.

Software sup-ports importingof bulk meta-data/contentsof digital ob-jects.

DoKS supportsto import bulkdigital objects.

EPrints sup-ports to importbulk digitalobjects.

Fedora sup-ports to importbulk digitalobjects.

Greenstonesupports toimport bulkdigital objects.

Software sup-ports importingof bulk digitalobjects.

SOPS sup-ports importingof bulk digitalobjects.

Software sup-ports to extractautomaticextraction ofkeywords fromthe full text ofthe documentsbased on thefrequency ofthe specificterms.

Software doesnot extract au-tomatic meta-data of digitaldocuments thatare imported.

Software doesnot extract au-tomatic meta-data of digitaldocuments thatare imported.

Software doesnot extractautomaticmetadata ofdigital docu-ments that areimported intothe repository.

Fedora au-tomaticallyextracts title ofthe documentand identifier ofthe document.

Greenstoneautomaticallrecognisesdate, encod-ing, file format,file size, lan-guage, numberof pages andsource detailsfor each object.

Software doesnot exatractautomaticmetadata ofdigital docu-ments that areimported.

SOPS doesnot importautomaticmetadata ofdigital docu-ments that areadded into therepository.

CDS-Inveniosupports meta-data exportin BibTex,Dublin Core,End Note,HTML, brief,HTML detailed,MARC, MAR-CXML, NLM,photocaptionsonly, portfolioformat.

Software sup-ports to exportdata into dublincore andMETS format.Generally datais exported asXML files.

DoKS supportsto export datainto XML for-mat.

EPrints sup-ports to exportmetadata intovariety of for-mats such asASCII Cita-tion, BibTex,DIDL, EP3XML, EndNote,METS, MODSetc.

Fedora sup-ports to exportcontents intoFOXML andMETS format.

Greenstonesupports to ex-port metadatainto METS,DSpace, MAR-CXML and GAformat.

MyCoRe sup-ports to exportmetadata inXML format.

SOPS sup-ports to exportdata intovariety of for-mats such asHaward StyleReference,BibTex, End-Note, ProCite,ReferenceManager, XMLetc.

Software sup-ports to exportbulk metadataof digital ob-jects.




Fedora sup-ports to exportbulk meta-data/contentsof digital ob-jects.

Greenstonesupports to ex-port bulk meta-data/contentsof digital ob-jects.

MyCoRe sup-ports to exportbulk digital ob-jects.

SOPS sup-ports to exportbulk metadata.

Software sup-ports to addpast versionsof each digitaldocument tocontrol differ-ent editionsof registeredobjects.

DSpace doesnot supportadding pastversions of dig-ital documents.

DoKS supportsadding pastversions of dig-ital documents.

EPrints doesnot supportadding pastversions of dig-ital documents.

Fedora has avery good fea-ture of addingdifferent ver-sions of thedigital docu-ments that areadded into therepository.

Greenstonedoes not sup-port addingpast versionsof digital docu-ments.

Software sup-ports to addpast versionsof digital docu-ments.

Software doesnot supportadding pastversions of dig-ital documents.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

66


CDS-Inveniosupport itsown accessionnumber foreach docu-ment that getsadded into therepository.

DSpace has itsown accessionnumber and itis called as aninternal ID.

DOKS create aunique id num-ber for everydocument, au-thor, CV, key-word etc. thatis added intothe repository.

EPrints createa unique nu-meric ID foreach docu-ment that getsadded into therepository.

Fedora sup-ports to createeither customaccessionnumber or de-fault accessionnumber andeach digital ob-ject is identifiedwith PID.

Greenstoneassigns OIDfor every digitaldocument thatis added intothe repository.

MyCoRe gen-erates its ownaccessionnumber forevery digitaldocument thatis added intothe repository.

Software gen-erates its ownaccessionnumber forevery digitaldocument thatis added intothe repository.

CDS-Inveniosupports weedout policy.

DSpace sup-ports weed outpolicy.

DoKS does notsupport weedout policy.

EPrints sup-port weed outpolicy.

Fedora sup-ports weed outpolicy.

Greenstonedoes not sup-port weed outpolicy.

MyCoRe doesnot supportweed outpolicy.

SOPS sup-ports weed outpolicy.

Softwaresupports todelete itemsfrom collec-tion/repositoryas well asmove objectsfrom onecollection toother collectioni.e. contentmapping.

Software sup-ports to deleteitems fromthe collectionbut supportto map itemsacross differentcollections.

DoKS sup-ports to deleteobjects fromthe reposi-tory. DoKSorganises alldocumentsadded intothe repositoryinto differentfolders.

EPrints sup-port to deleteitems fromthe repositrybut does notsupport anycross linkingof objects fromone collec-tion to othercollection.

Fedora sup-ports to deleteitems fromthe repository.Fedora addseach item intothe repositoryas a uniqueitem.

Greenstonesupports todelete itemsfrom the collec-tion but doesnot support tomove digitalobjects fromone collec-tion to othercollection.

MyCoRe sup-ports to deleteitems from therepository butdoes not sup-port to movedocumentsfrom one col-lection to othercollection.

SOPS sup-ports to deleteitems fromthe repositorybut each itemin SOPS isunique, it is notattached withany collection.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

67


No global per-sistent identi-fier scheme issupported bythe software.Software hasits own persis-tent ID numberfor all docu-ments that areadded into therepository.

DSpace sup-ports CNRIHandle systemidentifier forall the docu-ments that areadded into therepository.

Software doesnot have anypersistent iden-tifier schemebut it supportsto add anyoher persistentidentifer’s toevery thesisadded into therepository.

EPrints doesnot have anypersistent iden-tifier schemesupport.

Fedora sup-ports URI aswell as sup-ports GDRFregistry as wellas it supportsto add otherpersistentidentifier num-bers as well assuch as handleor DOI etc.

Greenstonedoes notsupport anypersistent iden-tifier scheme.

MyCoRe sup-ports UniformResourceName i.e. URNfor all docu-ments that areadded into therepository.

SOPS doesnot supportany persis-tent identifierscheme.

Software doesnot have anycapability tohandle an ob-ject’s changein the locationand state infuture withsame identifiernumber.



EPrints doesnot have anycapability tohandle an ob-ject’s changein the locationand state infuture with thesame identifier.

Fedora havecapability tohandle an ob-ject’s changein locationand state infuture withsame identifiernumber.

Greenstonedoes not haveany capabil-ity to handlean object’schange in thelocation andstate in futurewith the sameidentifier.

MyCoRe havecapability tohandle an ob-ject’s changein locationand state infuture withsame identifiernumber.

Software doesnot have capa-bility to handlean object’schange inthe locationand state infuture withsame identifernumber.


Table 12.2: Content Management

Content Management CDS-Invenio

DSpace DoKS EPrints Fedora Greenstone

MyCoRe SOPS

Does the system have proper workflow in place which handles differentsubmission processes?

Yes Yes Yes EPrintssup-portslimitedsub-missionwork-flow

No No Yes No

Create overall system administrator Yes Yes Yes Yes Yes Yes Yes Yes

Allows to submit documents by usersvia web

Yes Yes Yes Yes No No Yes Yes

System allows to set up submissionrules

Yes Yes No No No No Yes No

Define accept/reject policy for docu-ments added into the repository

Yes Yes No Yes No No Yes No

Allows multiple collections withinsame installation

Yes Yes Yes No No Yes No No

Home page for each collec-tion/community

Yes Yes Yes No No Yes No No

Allows to set different policies for dif-ferent collections


Allow to set different authorizationpolicies for different collection/items


Allow to edit metadata submitted byusers


Sends email notifications tousers/submitters/authors

Yes Yes No Yes No No No No

Sends email notifications to meta-data reviewer

Yes Yes No No No No No No

Sends email notification to reviewers Yes Yes No No No No No No

Sends email notification to adminis-trators

Yes Yes No Yes No No No No

Allow users to review completed con-tent


Allow users to review uncompletedcontent


Allow content administrator to reviewsubmissions


View pending content administrationtasks



Content Management CDS-Invenio

DSpace DoKS EPrints Fedora Greenstone

MyCoRe SOPS

Does system support to upload doc-uments through Librarian’s interfaceas well?

No No No No Fedorasup-ports touploaddocu-mentsthroughLibrar-ian’sinter-faceonly.

Greenstonesup-ports tosubmititemsthroughLibrar-ian’sinter-faceonly

No No

Does system provide easy way foradding/editing of records for Librar-ian as well as for remote user?

Yes Yes Yes Yes No Yes Yes Yes

Are supported file formats well docu-mented in the system? Can new fileformats be added in the system?

Yes Yes No Yes Yes Yes No No

"Does the repository software haveany access control lists, Internet ad-dress filters etc. that limit who is al-lowed to submit documents into therepository?"

Yes Yes Yes Yes Yesonlyfedora-adminusercansubmitdocu-ments.

No Yes Yes

Does the repository software main-tain audit logs that identify by whomand when documents are submittedinto the repository?

No Yes Yes No Yes Yes No Yes

"Does system support knowledge or-ganization systems such as ontolo-gies, classification systems for userswhile adding documents via web?"

Yes Yes No No No Yes Yes No

Does the system support digital ob-jects to be grouped into organizedstructure?

Yes Yes Yes Yes No Yes Yes No

Does the system support to generateauthority files?

No Yes(Au-thors& Sub-jects)

Yes(Au-thorsandKey-words)

No No Yes Yes(Au-thors,insti-tutesandsub-jects)"

No

Does the system allow digital objectto a member of multiple collectionsi.e. Content mapping?


Does system allow users to modify(add/edit/delete) metadata/completecontent added within the repository?

Yes Yes Yes Yes No Yes Yes Yes

Does the system show strength ofeach collection?



than Dublin Core such as MARC 21, METS, IEEE LOM etc. Default metadata entry

templates are supported in all software except Fedora. Realupdating and indexing is sup-

ported in all software except Greenstone. One has to rebuildthe collections in Greenstone

then only indexes gets updated. CDS-Invenio, DSpace, Fedora, Greenstone & MyCoRe

supports to upload provenance metadata. Provenance metadata is important from digital

preservation point of view. At present metadata crosswalk is supported by DSpace, Fedora

& Greenstone. Thesaurus building which is one of the important feature in digital libraries,

is supported in CDS-Invenio, DSpace & EPrints.

12.4 Classification

Table 12.4 lists all evaluation criteria related to classification. CDS-Invenio, Greenstone &

MyCoRe supports to enter classification number. DSpace software supports to group digi-

tal objects as per the keywords/thesaurus but does not support adding any class number to

each digital object. EPrints software supports to group digital objects as per the Library of

Congress subject heading lists. DoKS, Fedora & SOPS does notsupport any classification

system.

12.5 Information Search & Retrieval

Table 12.5 lists all evaluation criteria related to information search & retrieval. Meta-

data and full text searching is supported by all software. All software support boolean

search, basic & advanced search features. Truncation, Phrase searching, proximity search-

ing, stemming, fuzzy searching is supported in all softwareexcept EPrints. Thesaurus

based searching is available at present only in DSpace software.

12.6 Access Control Privacy and Management

Access control is very well handled inCDS-Invenio. It supports to define different roles for

different users. It records only name and email address of every user that is registered into

the repository. It has facility to show active, inactive users, guest users etc. Software allow

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

71

Table 12.3: Metadata Submission and Support


Software sup-ports to adddescriptive,administrativeand structuralmetadata.

Software sup-ports to adddescriptive,administrativeand structuralmetadata.

DoKS supportsto add descrip-tive metadatabut not ad-ministrativeand structuralmetadata.

EPrints sup-ports to adddescriptive, tosome extentadministrativeand structuralmetadata.

Fedora sup-ports to adddescriptive,structural andadministrativemetadata.

Greenstoneby defaultsupports toadd descriptivemetadata butit can be con-figured to enterstructural andadministrativemetadata.

MyCoRe sup-ports to adddescriptive,administrativeand structuralmetadata.

SOPS doesnot support toadd in detailany of themetadata typeas there isno mentionof any meta-data schemasupport inSOPS.

Software sup-ports to addTitle, Author,Affiliation,Language,Number ofPages, Dateof Creation,Keywords, Ab-stract, Author’sComments,Other Refer-ence Number

DSpace by de-fault supportsadding Author,title, OtherTitle, Date ofIssue, Pub-lisher, Citation,Series/ ReportNo., Identifier,Type, Lan-guage, SubjectKeywords,Abstract,Sponsors,Descriptionfields

DoKS by de-fault supportsadding Ti-tle, Author,Abstract, Pub-lisher, Publica-tion Date, FullText, Appen-dices, Type,Language,Rights, DegreeName, DegreeLevel, Disci-pline, Grantorof the Degree,Department,Awards, Sta-tus, PersistentIdentifier,volumes, col-lation, subtitle,title, notes,copies etc.

EPrints by de-fault supportsto add itemtype, format,description,visible to,license, em-bargo expirydate, title,abstract, cre-ators, corpo-rate creators,Divisions,PublicationDetails, Fun-ders, Projects,Email, Ref-erences,UncontrolledKeywords,Comments,etc.

Fedora bydefault sup-ports to addID, state, Con-trol Group,Versionable,Created, La-bel, MIMEType, FormatURI, AlternateID, FedoraURL for everydocument.

Greenstone bydefault sup-ports to add all15 elementsof Dc such astitle, creator,format, date ofcreation, sub-ject, language,file format, filetype etc.

MyCoRe bydefault sup-ports addingTitle, Au-thor, Origin,Description,Publisher,Contributor,Date, Type,Format, Iden-tifier, Source,Language,Keywords,Coverage, Re-lation, Rights,Size, Con-tact, Note andCitation.

SOPS by de-fault supportsto enter id,authors, year,title, source,summary, key-words, series,type, email,more, content,discussionsand ratings.

Software sup-ports adding/editing/ delet-ing of metadatafields.







Software sup-ports adding/editing/ delet-ing of metadatarecords.

Help mes-sages aregiven in eachmetadata fieldswhile enteringdata.


No help mes-sages aregiven in eachmetadata fieldswhile enteringdata.

For eachmetadata fieldproper helpis providedfor enteringdata along withexamples.

No help mes-sages aregiven in eachmetadata fieldswhile enteringdata.

Help mes-sages aregiven in eachmetadata fieldwhile enteringdata.

There are nohelp messagesgiven in eachmetadata fieldwhile enteringmetadata.


CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

72


Software hasTitle and Au-thor as amandatoryfields.

Software hasTitle and Yearas a manda-tory fields.

DoKS hasï£¡Titleï£¡ asa mandatoryfield.

EPrints hasItem Type,Title, Creator,Referenceand Subjectas mandatoryfields.

Fedora hasonly one fieldmandatoryi..e. Title orit is called asLabel.

There areno manda-tory fields inGreenstone.It automati-cally extractssome of themetadata fromdigital files.

Software hasTitle, Author,Type, Format,Languageand Rightsas mandatoryfields.

Software hasauthor, titleand year asmandatoryfields.

Software sup-ports UTF-8








Software sup-ports to allowto create andmanage vari-ety of differentmetadataschema.

DSpace cur-rently supportsonly DublinCore metadataschema.

DoKS currentlysupports onlyone metadataschema.

EPrints sup-ports onlyone metadataschema.

Yes, Fedoradefines cre-ating newmetadataschemas asï£¡behaviourdefinitionï£¡.

Software allowto create vari-ety of metadatasupport.

MyCoRe cur-rently supportsQualifiedDublin Coremetadataschema butit has capa-bility to adddifferent meta-data schemafor differentcollections.

There is nomention ofany meta-data schemasupported bySOPS.

Metadata fieldsand formatscan be cus-tomized.

DSpace hasinputforms.xmlfile which canbe used tocustomizemetadataforms andformats.

It is possibleto customizemetadata fieldsand formats.





Metadata fieldsand formatscan be cus-tomized.

Software sup-ports by defaultDublin Coreand MARC21 metadatastandard

Software bydefault sup-ports DublinCore metadatastandard.

DoKS supportsby defaultETD-MSDublin Coremetadataschema.

EPrints sup-ports onlyDublin Coremetadataschema.

Fedora sup-ports DC,METS, MPEG-21, DIDL, IEEELOM, MARCmetadataschema.

Greenstonesupports:New ZealandGovernmentLocator Ser-vice MetadataStandard(nzgls), RFC1807 Meta-data ElementSet, QualifiedDublin Core,DevelopmentLibrary Sub-set ExampleMetadata,GreenstoneMetadata Set,AustralianGovernmentLocator Ser-vice MetadataElement Set

Software atpresent sup-ports QualifiedDublin Coremetadatastandard.

No defaultmetadataschema sup-port for SOPS.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

73


Software hasdefault meta-data entrytemplates


DoKS has de-fault metadataentry template.

EPrints has adefault meta-data entrytemplate.

Fedora doesnot have anydefault meta-data entry tem-plate. Softwareimports anyXML basedmetadata.


MyCoRe hassingle meta-data entrytemplate.

Software hasdefault meta-data entrytemplate.

Metadata for-mats are welldocumented inthe software.

Metadata for-mats are welldocumented inthe software.

Metadata for-mats are notdocumented inDoKS.

Metadata for-mats are welldocumented inEPrints.

Metadata for-mats are notdocumented inFedora.

Metadataformats aredocumented inthe system.

Metadataformats aredocumented inthe system.

Metadataformats aredocumented inSOPS.

Software sup-ports differentinterface formetadataentry and cus-tomized datagets added intothe system.

It is possible tocreate differentinterfaces formetadata entryand it can becustomizedto get dataadded into thesystem but itdemands moreknowledgeabout DSpacecoding.

DoKS does notsupport to cre-ate different in-terface for en-tering data.

Software sup-ports to createdifferent inter-face for enter-ing data.

It is not pos-sible to createdifferent inter-faces for enter-ing data.

It is possible tocreate differentinterfaces formetadata entryand softwarehas capa-bility to addcustomizeddata into thesystem.

It is possible tocreate differentinterfaces formetadata entryand softwarehas capa-bility to addcustomizeddata into thesystem.

Software doesnot support dif-ferent interfacefor metadataentry.

There are noways by whichsoftware canverify addeddata.

There areno automatedchecks to verifyadded data.







There are noautomatedchecks for dateentering etc.






For date stringthere is auto-mated checkbut for otherfields there areno automatedchecks.


CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

74


Software doesnot have anyways by whichdata tamper-ing can becontrolled.








Software sup-ports realtime updatingand indexingof updatedcontents.


DoKS supportsreal time up-dating and in-dexing of con-tents.

EPrints sup-ports real timeupdating andindexing ofcontents.

Fedora sup-ports real timeupdating andindexing ofcontents.

Greenstonedoes not sup-port real timeupdating andindexing. Forevery itemadded into therepository onehas to rebuildthe collectionwhich is one ofthe drawbackof Greenstone.



Software sup-ports metadataextensibilityand complex-ity.


Software doesnot supportmetadata ex-tensibility andcomplexity.


It is possibleto have com-plex metadatafor every digitalobject.

Yes Green-stone supportsmetadata ex-tensibility andcomplexity.



Metadata ver-sioning is notsupported inthe software.








Provenancemetadata issupported bythe software.

DSpace sup-ports prove-nance meta-data andfollowing meta-data is added: - Name andemail addressof the submit-ter, uploadingdate and time,number ofbitstreamsuploaded, totalnumber ofbytes of eachbitstream,checksum dataof uploadedbitstream

DoKS doesnot supportprovenancemetadata.

EPrints doesnot supportprovenancemetadata.

Fedora sup-ports to adddifferent infor-mation abouta digital objectsuch as size ofthe file, createdby, total sizeetc.

Greenstonesupports toadd prove-nance meta-data.

MyCoRerecords prove-nance meta-data such asdigital docu-ment createdat and lastchanged withtime and date.

SOPS does notsupport anyprovenancemetadata.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

75


Metadatacrosswalk isnot supported.

DSpace sup-ports metadatacrosswalk.

Software doesnot supportmetadatacrosswalk.

EPrints doesnot supportmetadatacrosswalk.

Fedora sup-ports metadatacrosswalk.

Greenstonesupportsmetadatacrosswalk.

MyCoRe doesnot supportany metadatacrosswalk.

SOPS doesnot supportany metadatacrosswalk.

Thesaurusbuilding is sup-ported by thesoftware.

Thesaurusbuilding is sup-ported by thesoftware.

Software doesnot supportthesaurusbuilding.

EPrints sup-ports LC sub-ject headinglist.

Software doesnot supportany thesaurusbuilding.



SOPS doesnot supportany thesaurusbuilding.

No ontologysupport avail-able in thesoftware.








There are noways by whichsubmitted filescan be verified.

DSpace veri-fies the listedfile formatsand checkswhether thosefiles are sup-ported byDSpace thenonly thosefiles will beuploaded intothe repository.

DoKS hasthe facility toidentify filetype. If the fileis not identi-fied it uploadsthe file withï£¡unknownï£¡status.

EPrints has fa-cility to identifysubmitted fileand upload re-spective pluginfor that file.

Fedora has fa-cility to identifyuploaded file. Ifthe file is notMIME type Fe-dora throws er-ror.

Greenstonehas facility toidentify theuploaded filethrough avail-able plugins inGreenstone.

MyCoRe hasfacility to iden-tify file formatssubmitted intothe repository.If the file formatis not identi-fied it uploadsthat file asï£¡unknownï£¡format.

There are noways by whichit is possibleto verify sub-mitted file for-mats in SOPS.

While export-ing metadatasoftware doesnot supportchecksums.







Software doesnot supportchecksumswhile exportingmetadata.

Software sup-ports RAP pro-tocol.

DSpace sup-ports RAPprotocol.

DoKS does notsupport RAPprotocol.

EPrints sup-ports RAPprotocol.

Fedora sup-ports RAPprotocol.

Greenstonesupports RAPprotocol.

Software doesnot supportRAP protocol.

SOPS doesnot supportRAP protocol.


Table 12.4: Classification

Classification CDS-Invenio DSpace DoKS EPrints Fedora Green stone MyCoRe SOPS

Entering ClassNumbers

Yes No No No No Yes Yes No

Classification Sys-tem Support

Supports toadd any classnumber such asUDC/ DDC/ BC

No No No No Supports toadd any classnumber such asUDC/ DDC/ BCetc.

Supportsto addDDC classnumbers.

No

Grouping of Docu-ments as per classNumber

Yes Yes, asper key-words

Yes Yes, asper LCsubjecthead-ings

No Yes Yes No

Hierarchical Brows-ing Support

Yes Yes Yes Yes No Yes Yes No

to create different groups for different users, allow to define different user groups, allow

to limit access by role, file/object level, collection level, user/group level etc. Software

keeps track of passwords submitted by users and it allow end users to select his/her own

passwords. Access levels in CDS-Invenio can be generated atdifferent levels. Software

does not support access level through IP filtering or proxy filtering or credential based

filtering. Software does not support to allow to access certain collection for a specific

period.

DSpacecreates e-persons for all the members who register themselves through the web

browser and it is called as My DSpace. For every member DSpaceholds email address, first

and last name, list of collections for which the e-person wishes to be notified for new items,

password details etc. Software supports to add/edit/delete user profiles. DSpace supports

to define different roles for different users. DSpace does not keep detailed information

of every user who is registered into the repository. In DSpace for every user different

permissions are given for different roles. DSpace does not keep track of active and inactive

members. Software allow to create different roles, for different uses with different levels.

All passwords are encrypted and are stored into the database. Software does not assign

password for every user rather it allow end user to select his/her own password. DSpace has

mechanisms to retrieve forgotten passwords. DSpace supports to provide different action


Table 12.5: Information Search and Retrieval

Browsing CDS-Invenio DSpace DoKS EPrints Fedora Greenstone MyCoRe SOPS

Author/ Creator/Contributor

Yes Yes Yes Yes Yes Yes No Yes

Title of the docu-ment/ Title of thebook etc.

Yes Yes No Yes Yes Yes No Yes

Issue/ Date/ Date ofPublication

Yes Yes Yes Yes Yes Yes No Yes

Collection Yes Yes Yes No No Yes No NoCommunities No Yes No No No No No NoSubject Browsing Yes No Yes Yes Yes Yes Yes YesPublisher wiseBrowsing

Yes No No No Yes Yes No No

Table of contentsbrowsing

No No No No No Yes No No

Multi-dimentionalbrowsing

No No No No No No No No

Searching

Metadata fieldssearching

Yes Yes Yes Yes Yes Yes Yes Yes

Full Text Searching Yes Yes Yes Yes Yes Yes Yes YesBoolean (AND, OR,NOT) Searching

Yes Yes Yes Yes Yes Yes Yes Yes

Basic Search Yes Yes Yes Yes Yes Yes Yes YesAdvanced Search Yes Yes Yes Yes Yes Yes Yes YesPutting differentoperators whilesearching

Yes Yes Yes No Yes Yes No Yes

Truncation/ wild cardsearching

Yes Yes Yes No Yes Yes Yes Yes

Phrase Searching Yes Yes Yes No Yes Yes Yes YesProximity Searching Yes Yes Yes No Yes Yes Yes YesStemming Yes Yes Yes No Yes Yes Yes YesFuzzy Searching Yes Yes Yes No Yes Yes Yes YesPhonetic Searching Yes No No No No No No NoCase sensitive orcase insensitivesearching

Yes No No No Yes Yes No No

Term weighting Yes No Yes No Yes Yes No NoSearch history op-tion, reuse of query,query save option

Yes No No No No Yes No No

Boosting the term Yes Yes Yes No Yes Yes No NoRange searching Yes No No No No Yes No NoUse of Thesarus No Yes No No No No No NoExpand Search Yes No No No Yes Yes Yes NoLateral Searching No No No No No No No NoSearch support forspecial collections


Searching via tableof contents and clas-sification codes


Ability to browsesubject/ authorauthority files


PIC variant search-ing




Multilingual searchand retrieval

Yes Yes Yes Yes Yes Yes Yes No

Allow refinement ofsearches with quali-fiers

Yes No No No Yes Yes Yes No

Ability to group priorto search

Yes No No No No Yes No No

Spell checker sup-port


Refine searches Yes No No No Yes Yes Yes No

Sorting

Author Yes Yes Yes Yes No Yes Yes NoTitle Yes Yes Yes Yes No Yes Yes NoIssue Date Yes Yes Yes Yes No Yes Yes NoRelevance Yes No No No No Yes No No

levels for different groups as well as for different communities, collections and items. By

default all items added into the repository have a policy of ANONYMOUS read. DSpace

cannot define access to a particular collection or item for a specific period.

DoKS has a very good user database management. It allows to createdatabase of dif-

ferent users. The system administrator or root only can add different users with different

permissions for every user and can assign password for everyuser. Every user have to be

a member of at least one group then only he/she is authorized to submit/edit documents

into the repository. Software supports to add/edit/deleteuser profiles. Software supports

to define different roles for different users. For every userDOKS keep details such as user

account, password, description, primary group, salutation, first name, last name, affiliation

details, institution name, faculty, department, email, telephone, FAX, Cell Number etc.

For every group DOKS allow to provide permissions based on different types of groups

such as each user can be either from admingroup, authorgroup, broadcastgroup, editor-

group etc. DoKS does not keep track of active and inactive users. System allow to create

different roles, for different groups with different actions. It has facility to control access

to users at collection level, file/object level as well as user/group level. All passwords

are encrypted into the system and stored in a database. For the first time software assign

passwords for each user and later on each user can change the password assigned by the

system. End user cannot change the password but only adminuser has privileges to change

the password. DoKS access levels are defined as per the different groups and for groups it


allows to define access levels. Software does not have facility to allow to access a particular

collection for a specific period.

EPrints has a very good feature of keeping detailed information of every user who reg-

isters into the repository. For every user system keeps detailed information such as type

of user, email address, name, department, organization, address, country, homepage URL

and user preferences. System supports to add/edit/delete user profiles. EPrints have lim-

ited definition of defining roles. It allow to create user, editor and repository administrator

roles. No other roles such as metadata editor, metadata reviewer etc. can be created in

EPrints. EPrints store detailed information of every registered user. EPrints does not have

any provision to identify active and inactive members. Software does not create different

roles for different users and for different groups. EPrintsallow to give access to metadata

level information to all. The full text view can be controlled by allowing anyone, registered

users and repository staff only. EPrints supports to keep the items added into the reposi-

tory for a specific period. One can add embargo date for every item that is added into the

repository.

Fedora does not have any user management support. It supports to create only one user

account that is FedoraAdmin and only FedoraAdmin user is allowed to carry out different

transactions in Fedora. One of the important feature of Fedora is it allow to control access

to individual object through IP filtering as well as through proxy filtering. Other features

related to access control and privacy are not supported by Fedora. If Fez or Murador are

used Fedora supports to add different users etc.

Greenstonesupports adding different users through its web interface called as ’collector’.

When this feature was explored it did not work successfully.Since this function did not

work successfully with Greenstone’s version 2.75 many evaluation criteria related to access

control were not valid.

MyCoRe allows to create database of different users. The system administrator or root can

create different users with different roles and passwords.Software supports to add/edit/delete

user profiles. For every user MyCoRe records user account, password, description, primary

group, salutation, first name, last name, affiliation details, institution name, faculty, depart-

ment, email, telephone, FAX number and cell number details.MyCoRe allows to provide

permissions based on different types of groups such as each user can be either from admin-


group, authorgroup, broadcastgroup, editorgroup, readergroup etc. Software does not keep

track of active/inactive groups. MyCoRe allow to create different groups for different uses

and allow each document to be customized for each role/group. Software supports access

limits at file/object level as well as at user/group level. All passwords are encrypted into the

system and stored in the database. For the first time system assign passwords for each use

and later on each user can change the password assigned by thesystem. MyCoRe has very

good access control mechanism. It allows to control access by individual user from the

repository as well as allow to control access by IP authentication at different levels. My-

CoRe supports to provide access control to every digital object added into the repository

with date stamp.

SOPSusers are managed in a WODA database. Software supports to add/edit/delete user

profiles. SOPS record user name, given name, family name, email, title, affiliation, country

and address for every user that is added into the repository.SOPS software does not have

any work flow. It does not give any permissions for different users. SOPS keep track

of active and inactive members. Software does not support tocreate different groups for

different users. Software does not allow access limits at different levels. Software assign

passwords for each user. System allow end users to select their own passwords. Software

supports to retrieve forgotten passwords. Software does not provide access to the digital

library through IP source filtering or through proxy filtering. System does not have any

feature to support access to the collections for a specific period.

12.7 Authentication and Authorization

CDS-Invenio has multiple authentication methods that let the repository administrator to

define different levels of access and restrictions according to the users. CDS-Invenio is well

designed for setting different authentication and authorization methods than DSpace. It has

a very good authentication & authorization support. Software supports to create complex

configurations for different roles, for different collections with different privileges. Soft-

ware supports to restrict access to contents through login name and password authentica-

tion. Software supports to have a super user/admin user who can perform any operation in

the system. CDS-Invenio also supports to have external authentication mechanisms. Soft-

ware supports to define different roles such as content developers role, administrator role,


contributor role, general user’s role, metadata reviewer’s role etc.

DSpacesupports to set different authorization policies. Authorization system in DSpace

is based on associating actions with objects and the lists ofpeople who can perform them.

Software supports to set different roles for different members for different collections. Soft-

ware support to have a super user/admin for all actions in thesystem. Software supports to

use an external authentication mechanism such as LDAP. Software supports to have con-

tent developer role, administrator role, general user, metadata reviewer etc. Authentication

and authorization in DSpace is well designed and it is one of the best feature in DSpace.

DoKS software supports to provide setting different authorization policies. It supports to

restrict access only based on login and password. Software supports to restrict access on

different collections, items in collections viewing. Software supports to generate super

user/admin who is overall manger/administrator of the software. System can create differ-

ent roles within the system. It can be configured for externalauthentication mechanisms

such as LDAP. Software has capabilities to display only those pages that are pertinent to

each user that he/she is able to see. Software supports to create different roles such as

content developers role, administrator role, contributorrole, general user etc.

EPrints software supports setting authorization policies with limited support. Software

supports to restrict access based on login and password. EPrints software supports autho-

rization privileges based on item full view with permissions such as viewed by anyone,

registered users only and repository staff only. Software supports only three roles such as

users, editor and repository administrator. Software supports to generate super user/admin

for overall manger/administrator of the software. Software does not support to define dif-

ferent roles with the system. EPrints does not use any external authentication mechanism.

Fedora does not support any authentication and authorization. In Fedora only FedoraAd-

min can submit documents into the repository. None of the other features related to authen-

tication and authorization are supported by Fedora. Fedoracan be configured with external

authentication mechanism such as LDAP.

Greenstonedoes not support any authentication and authorization. In the documentation

manual there is mention of incorporating an authenticationscheme which can be used

to restrict people who are allowed to carry certain actions,for different collections for

different members but when this feature was explored it did not work successfully.


MyCoRe supports to set different authorization policies. Software supports to restrict

access to contents through password authentication and through IP filtering as well. By

default, MyCoRe shows all documents added into the repository to end users but detailed

view is restricted based on different authorization policies. Software supports to generate

different roles for different members for different items/collections. Super Admin account

is created in the software. MyCoRe can also be configured withexternal authentication

mechanism such as LDAP. Software supports to create different roles such as content de-

veloper role, administrator role, contributor role etc.

SOPSdoes not support to set different authorization policies. Many features related to au-

thentication and authorization are not supported by SOPS. Software only supports to create

general user and allow end user to submit documents and software allow to create one ad-

ministrator account. None of the other features related to authentication and authorization

were valid for SOPS.

12.8 Interoperability

Table 12.6: Interoperability Support

Software Z39.50/OAI-PMH Support Harvesting Software used SRU/ SRWSupport

OpenURL Sup-port

CDS-Invenio OAI-PMH 2.0 protocol. It has its own harvesting soft-ware.

Yes Yes

DSpace OAI-PMH 2.0 protocol. PKP harvesting software Yes YesDoKS OAI-PMH 2.0 protocol. OAICAT harvesting software No YesEPrints OAI-PMH 2.0 protocol. PKP harvesting software No YesFedora OAI-PMH 2.0 protocol. No information about which

harvesting software is used isfound anywhere.

Yes Yes

Greenstone Software supports Z39.50 proto-col as well as OAI-PMH 2.0 pro-tocol.

Software uses its own OAIsoftware known as oaiserver.

Yes No

MyCoRe Software supports Z39.50 proto-col as well as OAI-PMH 2.0 pro-tocol.

Software uses its own harvest-ing software.

Yes Yes

SOPS OAI-PMH 2.0 protocol. No information about whichharvesting software is used isfound anywhere.

No No

Table 12.6 shows that all software support OAI-PMH protocol. Some of the software use

their own harvesting software. Greenstone & MyCoRe software support Z39.50 protocol


as well. SRU/SRW support is provided by CDS-Invenio, DSpace, Fedora, Greenstone &

MyCoRe. OpenURL support is provided by all software except Greenstone & SOPS.

12.9 Ease of Deployment of Each Software

Table 12.7 lists all evaluation criteria related to installation of each software. Installation

of Greenstone is the easiest task only Greenstone software has automatic installation script

file. All other software demand high knowledge of configuringbackend database, web

server, file permissions, setting environments etc. There are no automatic installation script

files available for other software.

12.9.1 Hardware/Software Requirements

No specific hardware requirements are mentioned forCDS-Invenio. Though the first ver-

sion of software is yet to release, software has been bringing out new versions frequently

with several new features. Software does not have any procedure to monitor and receive

notifications when hardware technology changes. The software creators have process to

stay current with the latest operating security fixes.

There are no specific hardware requirements forDSpaceinstallation except UNIX. DSpace

has been widely used by a large community. Since it is jointlydeveloped by HP and MIT

regularly new versions of DSpace are available for download. Software does not have

any procedures in place to monitor and receive notificationswhen hardware technology is

changed.

There are no specific hardware requirements forDoKS installation.Software has brought

out sofar only three releases but the latest release is not working properly. Software does

not have any procedures in place to monitor and receive notifications when hardware tech-

nology is changed.

For installingEPrints atleast 1 GHz processor, 512 MB RAM and 40 GB disk space is

specified in documentation manual. EPrints has been actively used by a large community

among all the selected software. Software has been regularly bringing out new versions at

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

84

Table 12.7: Software Installation


Automaticinstallationscript

No automaticinstallationscript avail-able.





Yes, singlefile is thereand it installsall relatedcomponents.


No Automaticinstallationscript avail-able.

Disk spaceused

700 MB 500 MB 100 MB 130 MB 349 MB 111 MB 268 MB 13 MB

Time requiredto install eachsoftware

It is difficult toinstall CDS-Invenio. Ittakes morethan a dayto installsuccessfullyCDS-Invenio.

It takes fewhours to suc-cessfully installDSpace.

It is tricky toinstall DoKS.Installation ofDoKs needsexpertise asthere is needto change dif-ferent file pathswhich is notmentioned inthe installationprocess. Ittakes a day tosuccessfullyinstall DoKS.

It is easy toinstall EPrints.It takes aroundtwo to fourhours tocompletelyconfigure thesoftware.

If all environ-ments are setproperly it iseasy to installFedora. Ittook aroundtwo hours tocompletelyconfigurefedora.

InstallingGreesnstonesoftware isvery easy. Ittakes hardlyany time toinstall thesoftware.

Installing My-CoRe is easy.It took abouttwo to threehours to dosuccessfulinstallation ofMyCoRe

Installation ofSOPS is noteasy. Onehas to changepaths in manyfiles. It requiresexpertise helpin handlingSOPS instal-lation. It takesaround four tofive hours toinstall SOPS.

Documentationhelp availableand useful forinstallation

Yes Yes Yes Yes Yes Yes Yes but avail-able in German

Yes but not indepth.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

85


Environmentsneeded to setfor installa-tion of eachsoftware

No environ-ments areneeded to setfor installation.

JAVA, Tomcat,Ant environ-ments areneed to set forinstallation

JAVA and ANThome envi-ronments areneeded to set.


JAVA, Tomcat,Fedora homeenvironmentsare needed toset

JRE environ-ments arerequired tobe set forGreenstoneInstallation.

MYCORE_HOME, DOC-PORTAL_HOME, ANT_HOME, JAVA_HOME envi-ronments areneeded to beset.


Operating Sys-tems on whichsoftware canbe installed

POSIX,Linux, So-laris, SunOS

FreeBSD, De-bian, Ubuntu,Mandriva,OSX, MacOS X, RedHat, Gentoo,SLES9 as wellas windows(with limitedsupport)

Any Linux fla-vor or windows

Linux, Solaris,BSD, OSX aswell as Win-dows

Windows 2000,NT, XP, Solarisand any Linuxflavour or MacOS

Greenstonecan be in-stalled on all32-bit win-dows (95/ 98/2000/ XP/), allPOSIX(Linux/BSD/ UNIX-likeOSES), OS X

MyCoRe canbe installedon 32-bit MSWindows (95/99/ NT/ 2000/XP), All POSIX(Linux/ BSD/UNIX-like),Linux, Solaris,IBM, AIX andMacOS

Linux, Unixas well aswindows

Programminglanguagesused

Python, LISPand PL/ SQL

JAVA andserver sideJAVA technolo-gies includingJAVA servlets,JSP

Java frame-work tools

PERL CORBA andJAVA

C++ , JAVAand Perl

Java, XSL(XSLT/ XPath/XSL-FO)

Perl

Database sup-ported at backend

MySQL PostGreSQLand Oracle

MySQL MySQL MySQL, Post-GreSQL, Ora-cle and Mckoi

GDBMdatabase i.e.Gnu DatabaseManager

MySQL,HSQL, IBMContent Man-ager, Oracle,DB2

WODA

Web serverused

Apache WebServer

Apache WebServer

Apache WebServer

Apache WebServer

Apache WebServer

Apache WebServer/ IISWeb Server

Apache WeServer, JettyWeb Server

Apache WebServer

Java servletengine needed

No Apache Tom-cat or JakartaTomcat

Apache Tom-cat

No ApacheTomcat andApache Axis(SOAP) servlet

No Apache Tom-cat

No

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS3

86


System Sup-port/ Mainte-nance

Documentation/manuals

Online Doc-umentationavailable athttp:// cdsinve-nio. cern.ch/invenio/ docu-mentation.html

Online Doc-umentationavailable athttp://www.dspace.org

Online Doc-umentationavailablethroughwiki pagehttp://doks.khk.be/wiki/index.php/Main_Page

Online Doc-umentationavailablethroughwiki pagehttp://wiki.EPrints.org

Online Doc-umentationavailable athttp://www.fedora.info

Online Doc-umentationavailablethroughwiki pagehttp://wiki.green-stone.org/wiki/ index.php/Manual

Online Doc-umentationavailable athttp://www.mycore.de/content/ main/documenta-tion.xml

Documentationmanual avail-able but it isnot in depth.

Mailing lists/discussionforums

CDS-Inveniohas threemailing listssuch [email protected],[email protected],[email protected].

http://sourceforge.net/mail/ ?group_id=19984

No mailing listavailable

EPrints hasonly techni-cal mailinglist such ashttp://www.EPrints.org/tech.php/

Fedora hastwo mailinglists such ashttps://lists.source-forge.net/ lists/listinfo/ Fedora-commons-developers,https://lists.source-forge.net/ lists/listinfo/ Fedora-commons-users

Greenstonehas two mail-ing lists suchas [email protected]@ lists.scms.waikato.ac.nz

MyCoRe hasuser mailinglist and devel-opers mailinglist suchas [email protected], mycore-developers@lists. source-forge. net

No mailing listavailable.

Wiki pages https://twiki.cern.ch/ twiki/bin/ view/ CDS/Invenio

http://wiki.dspace.org

http://doks.khk.be/ wiki/index.php/Main_ Page

http://wiki.EPrints.org

http://Fedora.info/wiki

http://wiki.green-stone.org/ wiki/index.php/Green-stoneWiki

http://cmsobj.rrz.uni- ham-burg.de:50080/ cm-swiki/ My-CoReWikiWiki

No wiki pageavailable.

Help desk sup-port

No http://libraries.mit.edu/ dspace-mit/info/ dspace-help.html

No No http:// source-forge.net/forum/ fo-rum.php?forum_id=38148

No No help desksupport avail-able.

Ease of systemadministration

Software iscomplex toconfigure

System ad-ministrator caneasily config-ure softwarefor differentusers.

It is easyto configureDoKS fordifferent users.

EPrints canbe config-ured easily fordifferent users.

Fedora is notmeant for dif-ferent users.Only fedoraAd-min can submitdocuments tothe repository.

ThoughtGreenstonehas abilityto configurefor differentusers thisfeature doesnot work prop-erly through’collector’

It is easy toconfigure My-CoRe for differ-ent users.

SOPS is easyto configure fordifferent users.


a frequent intervals. Software does not have any proceduresin place to monitor and receive

notifications when hardware technology is changed.

Fedora installation does not require any specific hardware configuration. It can be installed

on any PIV machine with 512 MB RAM. Fedora is well maintained by its developers and

regularly new versions are brought out. Software does not have any procedures in place to

monitor and receive notifications when hardware technologyis changed.

Greenstonerequires minimum P III or PIV machine for installation. Since 1998, Green-

stone developers are bringing out continuously new versions. A major change is made in

Greenstone version 2 and now Greenstone version 3 is available but it is not yet stable.

Software does not have any procedures in place to monitor andreceive notifications when

hardware technology is changed.

MyCoRe can be installed on any PIV machine though no specific hardware requirements

are mentioned on the MyCoRe site. In Germany MyCoRe has been actively used and

regularly new versions of MyCoRe are brought out. Software does not have any procedures

in place to monitor and receive notifications when hardware technology is changed.

SOPSworks well with Intel Pentium 133 MHz class machine. SOPS hasnot brought out

any new versions after version 1.0. Software does not have any mechanisms to monitor

and receive notifications when hardware technology changes.

12.9.2 Security

Table 12.8 lists evaluation criteria related to system security. All software have secure

database connection through login and password except Greenstone. Greenstone software

database access is not available to end users. DSpace, DoKS,Fedora & MyCoRe supports

data encrytion. Fedora also supports digital signature feature. DSpace, DoKS, EPrints

supports md5 checksum. Fedora supports data integrity stamp for the datastream which

can be calculated using one of many standard algorithms suchas MD5, SHA-1, SHA-256,

SHA-384, SHA-512.


Table 12.8: Security & System Level Security

Security & SystemLevel Security

CDS-Invenio

DSpace DoKS EPrints Fedora Green-stone

MyCoRe SOPS

Data Encryption No Yes Yes No Yes No Yes No

Digital Signatures No No No Yes Yes No No No

Server Security Yes Yes Yes Yes Yes No Yes Yes

Fixity No Softwaresup-portsmd5check-sum.

No Softwaresup-portsmd5check-sum.

Fedora supports dataintegrity stamp for thedatastream which canbe calculated using oneof many standard algo-rithms such as MD5,SHA-1, SHA-256, SHA-384, SHA-512

No Softwaresupportsmd5 check-sum.

No

Firewall Support No No No No No No No No

12.9.3 General features supported by each software

12.9.3.1 Back end maintenance: None of the software requireany back end maintenance.

12.9.3.2 RSS Support: CDS-Invenio, DSpace, DoKS, EPrints,SOPS provide RSS support.

Greenstone, Fedora, MyCoRe does not provide any RSS support.

12.9.3.3 Upgrading Software: Upgrading CDS-Invenio, DoKS, EPrints, Fedora, MyCoRe,

Greenstone is trivial. DSpace upgrading is not very simple.If the major version re-

lease difference is there, one has to upgrade back end database as well as the DSpace

version which not very simple for the end user. Upgrading DSpace requires more

knowledge of backend technology. No new versions of SOPS aremade available

after the first release hence how to upgrade these software isnot required.

12.9.3.4 Data Migration: CDS-Invenio, DSpace, DoKS, EPrints, Fedora, Greenstone, My-

CoRe support migration of data from one repository softwareto another repository

software. No information available for data migration for SOPS software.

12.9.3.5 Ranking Algorithm: CDS-Invenio supports to rank all documents that are added into

the repository and SOPS software supports to rank each document that is added into

the repository in the scale of poor, average, good, very goodand excellent. No other

software support any ranking algorithm.


12.9.3.6 Known issues/Bugs in the system

CDS-Invenio data entry has one bug, which is while submitting documents into the

repository one has to apply a patch which needs to be used to get this function work-

ing. The patch is websubmit_engine.py. There are no major issues in DSpace but

DSpace data import/export from different instances of DSpace is not very easy to

carry out. DoKS document submission is not very easy. Systemthrows error while

submitting documents into the repository. One of the main drawback of Greenstone

is, it does not have incremental indexing. For every item that is added into the reposi-

tory one has to rebuild the collection. If there are millionsof records then the rebuild

process takes lot of time, which is not the case with other software. The “collector”

option available with Greenstone does not work properly. There is no ’log out’ option

available for web interface which is one of the main bug in Greenstone. MyCoRe

installation has a small bug. While installing MyCoRe one has to rerun ’ant create’

and ’ant webapps’ commands twice and then only it gets successfully installed. One

of the major issue with SOPS is its installation. One has to change several paths in

many files while installing SOPS and then only it gets successfully installed.

12.9.3.7 Submitting Error Reports: CDS-Invenio, DSpace allow to submit error reports for

any error while using the software but DoKS, EPrints, Fedora, MyCoRe, SOPS does

not allow to submit any error reports while using the software.

12.9.3.8 Number of developers working for the software

Table 12.9: Number of Developers Working for Each Software

Name of the Software Number ofDevelopers

CDS-Invenio 2DSpace 14DoKS 6EPrints 6Fedora 16Greenstone 9MyCoRe 16SOPS No information

available.


As shown in Table 12.9 maximum number of developers are working on Fedora and

MyCoRe followed by DSpace and Greenstone.

12.9.3.9 Total Number of Downloads of the Software

Table 12.10: Total Number of Downloads of Each Software

Software Total Number of Downloads

CDS-Invenio No information available.DSpace 3926 (7th March 2008)DoKS 173 (23rd February 2008)EPrints No information available.Fedora No information available.Greenstone No information available.MyCoRe 27 (3rd March 2008)SOPS No information available.

DSpace is downloaded maximum number of times as shown in Table 12.10. DSpace,

DoKS and MyCoRe are available through sourceforge site hences different statistics

are available but other software are not available through sourceforge site hence their

total number of downloads are not maintained by the softwarecreators.

12.9.3.10 Strength of the Community

Table 12.11: Strength of the Community of Each Software

Software Total Numberof downloads

CDS-Invenio 19DoKS 6DSpace 307EPrints 251Fedora 28Greenstone Not KnownMyCoRe 17SOPS 12

Table 12.11 shows that there are more number of installations of DSpace followed by

EPrints. Greenstone is heavily used in Asian countries but many of the installation of


Greenstone are running on Intranet servers hence it is difficult to know total number

of users of Greenstone [1]. CDS-Invenio, Fedora, MyCoRe, SOPS and DoKS have

less user base.

12.9.3.11 License Terms and Conditions

Table 12.12: License Terms and Conditions

Software License Terms and Conditions

CDS-Invenio GNU General Public LicenseDSpace BSD Distribution LicenseDoKS GNU General Public LicenseEPrints GPL License terms and conditionsFedora Mozilla Public LicenseGreenstone GNU General Public LicenseMyCoRe GNU General Public LicenseSOPS No License specified

Table 12.12 shows license terms and conditions for each software. Each software is

available under different license terms and conditions. For SOPS software there is

no license terms and conditions specified.

12.9.3.12 Users Mailing List used by Each Software

Table 12.13: Mailing List of Users of Each Software


2002 132003 33 89 148 683 102004 147 378 269 899 662005 203 336 250 716 1015 1622006 87 463 2000 1202 1054 1922007 330 552 3000 835 1079 3182008 100 107 434 227 226 69

Total 913 1925 5684 3397 4956 817

Table 12.13 provide a tabular view of mailing list of users ofeach software. Though

CDS-Invenio was made available in 2002, the number of installations as well as

mailing list used by the user’s of CDS-Invenio is not as largeas compared to EPrints,


Greenstone, Fedora. EPrints, Greenstore, Fedora mailing list is used by large number

of users. EPrints has the largest number of requests sent through its mailing list

followed by Greenstone. SOPS and DoKS software yet does not have any mailing

list due to small number of user community. DSpace software is also used by large

community and number of requests sent to DSpace are increasing day by day.

12.9.3.13 Training programs conducted by each software

DSpace user meeting is taking place every year since 2004. DSpace workshops

are held all over the world regularly. In India DRTC has takena leading role in

popularizing DSpace at various organizations and have conducted several workshops

on DSpace.

EPrints workshops are conducted regularly at local, regional, national and interna-

tional levels. NCSI, Bangalore has conducted several training programs on EPrints

in India.

Greenstone is one of the popular open source software. Thereare many workshops

held at national and international level for Greenstone. InIndia, IIM Kozhikode has

been identified as a Greenstone support team for South Asia.

There are no training programs conducted for CDS-Invenio, DoKS, Fedora, SOPS

and MyCoRe software.

12.9.4 Architecture of the Software

CDS-Invenio Architecture of CDS-Invenio is complex architecture. The key feature of

CDSware’s architecture is its modular logic where each module carries out a specific and

defined functionality. Software does not support distributed database management. There

is no mention about grid architecture found anywhere in the literature.

DSpace architecture is three layer architecture, including storage, business and applica-

tion layers. Software supports to store data and actual filesin different areas. DSpace also

supports grid architecture.

DoKS No information was found about architecture of DoKS.


EPrints software has several data objects within the PERL modules torepresent runtime

entities such as users, e-prints, subjects etc. EPrints canbe configured as centralised/

distributed database.

Fedora architecture is based on the concept of object-oriented programming. Fedora

employs XML and METS to create digital objects by encapsulating content, along with

metadata about the content and actions that can be performedon the content. One of the

important feature of Fedora architecture is it has the flexibility to deal with the diversity of

electronic record types, supports versioning to preserve access to contents. Fedora supports

grid architecture.

Greenstone The key components in Greenstone architecture are the receptionist and the

collection server. The receptionist provides the user interface, dispatching requests to the

appropriate collection server or servers, and aggregatingresults for display back to the user.

Another significant part of Greenstone architecture is plug-ins and classifiers. Plug-ins

parse and extract metadata from imported documents. Classifiers create browse indexes.

MyCoRe No information about MyCoRe architecture was found any where.

SOPS architecture is modular architecture allowing different modules to be easily in-

cluded, left out, added or replaced relatively easily.

12.9.5 Scalability

CDS-Invenio, DSpace, Fedora and EPrints are scalable in terms of storage and retrieval.

These software have been tested with millions of records. But other software such as

Greenstone, MyCoRe, DoKS and SOPS does not have any information about testing of

millions of records uploaded into these software.


12.9.6 Storage

CDS-Invenio, Fedora & Greenstone supports to store compressed file formats to save disk

space. It also supports compression/decompression techniques.

DSpace, DoKS, MyCoRe & SOPS does not support any compressionand decompression

technique. It does not support to store files if available in compressed file formats.

EPrints supports to store files in compressed file formats butdoes not support compression

and decompression techniques.

12.9.7 Backup/Restore Facility

None of the software selected for evaluation provide any backup/restore facility. All soft-

ware used for the study depend on the system level backup. Forbackup one has to take

backup of system files as well as database files and restore them accordingly.

12.10 User Friendly Interface

CDS-Invenio allow to modify the user interface through an API or through scripts. Soft-

ware supports to customize user interface. It also supportsto customize user interface in

any local language. At present user interface is available in 17 languages. User interface is

same for the Librarian and for the end user. All functions in CDS-Invenio are carried out

through web interface. System provide online help for the users. Software supports multi-

lingual access support and system allow users to submit feedback on system problems.

DSpace user interface can be easily customized if one has knowledgeof JSP. DSpace

user can change complete look of the user interface. DSpace supports to localise user

interface in any language. It is easy to use DSpace user interface for Librarian as well as

for end user. User interface is same for the use of Librarian and end user. All functions in

DSpace are carried out through web interface. DSpace provides online help for using the

software. Software has multilingual access support. System allow users to submit feedback

on system problems.


DoKS It is possible to completely customize DoKS user interface.Software supports to

localise user interface in any language. DoKS user interface is not very easy for use either

for the Librarian or for the end user though user Interface issame for the Librarian and for

the end user. All functions in DoKS are carried out through web interface. DoKS supports

multilingual access support. System does not allow users tosubmit feedback on system

problems.

EPrints It is possible to completely customize EPrints user interface if the end user has

knowledge of PERL. Since EPrints supports UTF-8 it is possible to create user interface in

any localized language. User interface in EPrints is same for the Librarian and for the end

user. There is no online help provided for all operations that are carried out by the user or

by the Librarian. System allow users to submit feedback on system problems.

Fedora It is possible to customize user interface of Fedora. Fedorauser interface for

Librarian and for end user is different. It is not very easy touse Fedora Interface for

Librarian. The terminologies used in Fedora are complex hence it takes time to understand

how Fedora works. Software does not provide any help for end user. Software does not

provide multilingual access support. System does not allowusers to submit feedback on

system problems.

Greenstone user interface can easily be customized if the end user has knowledge of

PERL. Software allows to change header, footer and overall web interface of the system.

Greenstone also has one of the unique feature of creating a text only interface for visually

impaired users. Greenstone’s user interface at present is available in many languages such

as Arabic, Armenia, Bengali, Catalan etc. The Greenstone’suser interface is currently

available in more than 40 languages. Greenstone’s user interface is very easy to use for ex-

perienced and non experienced users. The user interface forLibrarian and for the end user

is different in Greenstone.Software does not allow to submit feedback on system problems.

MyCoRe It is possible to customize user interface of MyCoRe. MyCoResupports to

localize user interface in any language. MyCoRe user interface is very easy to use for the

experienced and non experienced staff. All functions in MyCoRe are carried out through


web user interface. No help is provided for using the MyCoRe.MyCoRe supports mul-

tilingual access support. Software does not have any provision to provide feedback on

system problems.

SOPS It is possible to customize user interface of SOPS. Softwareallow to change

header, footer, theme etc. as per the end users requirements. Currently SOPS interface

is available in English, German and Slovenian Language. SOPS user interface is same for

Librarian and for the end user. Software provide web based interface for all its functions.

Software can support multilingual access support.

12.11 Usability

CDS-Invenio is not very easy to use for the Librarian as it has complex functionality.

One has to have proper command on using the software. Searching in CDS-Invenio is

easy and end user can find his/her way to information quickly.Help features in CDS-

Invenio are user friendly and they answer to how to search forthe information through

CDS-Invenio. Of course, these help feature do not provide technical answers. Software

supports to provide end users to give user opinions on the webas well as it has support

to fill up online user feedback form which is one of the unique feature of CDS-Invenio.

Software supports web usage analyzer based on general web site hits, site hits per day,

unique visitors per day, search collection usage analysis,search engine query analysis,

user basket statistics, user alert statistics etc. which are unique features of CDS-Invenio.

It also generates ranking data for ranking search results based on methods like : word

similarity, similar records, combined methods etc.

DSpace It is easy to use DSpace web interface for searching records as well as easy

to use for the Librarian/Author etc. End user can easily find his/her ways to information

quickly and easily. DSpace help features provide general help but software does not support

any technical help feature. DSpace supports to generate different usage statistics such as

number of item views, number of collection visits, number ofcommunity visits, number

of OAI requests, user logins, most popular searches etc. DSpace also supports to show


results of statistical analysis on monthly basis or total statistical analysis and this statistical

analysis can be made available to public or restricted to system administrator access.

DoKS does not provide any help message while searching neither its documentation

available is very extensive. It is not very easy for the library staff to understand how DoKS

functions. DoKS does not provide any help features for searching documents. DoKS does

not provide any usage statistics reports. DoKS user interface for end users available is not

very easy to use.

EPrints is easy to use for the Librarian as well as for the end user for searching. User can

easily be able to find information through EPrints. EPrints provides general help features

for the end users but does not give any technical answers. EPrints supports to generate

all usage statistics such as usage patterns, use of materials, who uses what, when for what

reasons etc.

Fedora is not very easy to use for the Librarian as well as for the end users. The termi-

nologies used in Fedora are difficult for the end user to understand. For the end user it is

not very easy to search documents through Fedora. No help features are provided with the

user interface in Fedora. Fedora does not provide any usage statistics.

Greenstone librarian’s interface as well as user interface is easy to use. End user can

easily be able to find information from Greenstone digital library. Greenstone does not

provide extensive help feature. It gives general outline ofhelp but it does not cover all

aspects as required by a newcomer. Greenstone supports usage statistics at limited level

such as it keeps track of use of materials and who uses what andwhen.

MyCoRe is easy to use for the Librarian as well as for the end user. Enduser can eas-

ily navigate through different links and can find the information through MyCoRe portal.

MyCoRe does not provide any help feature for searching and retrieval which is one of the

drawback of MyCoRe. MyCoRe does not provide any usage statistics data.


SOPS is easy for use either for the Librarian or for the end user. End user can easily

search through search interface provided with the SOPS. General help is provided with the

SOPS but it does not provide any technical help support. SOPShas very good feature of

keeping track of all activities carried out in SOPS and it is able to provide different usage

statistics such as how information is used, who uses what andwhen etc.

12.11.1 Transaction Log Analysis

CDS-Invenio store error log files in apache error log. It also stores all search history

requests carried out into the repository and stores that data in query log file.

DSpace keeps all log data into log directory where dspace.log file records all actions

carried out in DSpace. DSpace does not store any query log data.

DoKS keeps all logs data in doks.log file where it records error logs and actions carried

out by users. DoKS software keep track of all query’s submitted to the system and stores

it as a query log file.

EPrints uses Apache Server log file for recording all actions carriedout in EPrints.

EPrints software does not have any separate log directory/file in its area to track all ac-

tions. EPrints supports to store search history log data. Itstores all search history requests

carried out into the repository as per the user ID numbers.

Fedora keeps error logs in client as well as server log directory of Fedora. Fedora client

keeps detailed log of all items ingested into the repositoryas well as Fedora server keeps

log of services initialised by the Fedora repository. Fedora does not keep record details of

queries submitted to Fedora software.

Greenstone keeps usage logs, error logs files in /greenstone/etc directory. It does not

record details of queries submitted to Greenstone software.


MyCoRe does not record any error, user, query logs.

SOPS keeps detailed log of all actions carried out in the software. It keeps usage and

error log files. It records all actions such as time duration,actions carried out by each user

etc. Software also records details of queries submitted to the SOPS repository by individual

users.

12.12 Copyright/Policy Issues

CDS-Invenio has capability to provide details about managing contract agreements for

all digital objects that are added into the repository. Software has capability to control

access to digital objects based on access control list to maintain copyright issue.

DSpace has the facility to keep track of all documents that are addedinto the repository

along with their copyright details. DSpace also supports tocontrol access based on access

control list based on login and password. Software also supports to record rights policies

for every document that is added into the repository.

DoKS does not have any provision to maintain contract agreement details for each dig-

ital document. Software supports to control access by IP address as well as by different

authorization procedures.

EPrints supports to allow to keep licensing conditions for individual digital objects with

following options as well as software supports to add any other third party license details.

Access to EPrints is controlled by user login and password.

License unspecifiedCreative Commons AttributionCreative Commons Attribution Non-commercialCreative Commons Attribution Non-commercial No DerivativesCreative Commons Attribution Non-commercial Share AlikeCreative Commons Attribution Public Domain DedicationCreative Commons Attribution GNU GPL (Software)Creative Commons Attribution GNU LGPL (Software)


Fedora allows to maintain contract agreements for all the digital documents that are

added into the repository and supports to restrict access tothe individual objects through

IP filtering.

Greenstone does not have any facility to manage, store contract agreements for all the

digital documents that are added into the repository.

MyCoRe does not have any provision to maintain contract agreementsfor all the docu-

ments that are added into the repository, It supports to control access to digital documents

through IP filtering as well as through login and password.

SOPS does not have any provision to maintain contract agreement details for all the

documents that are added into the repository. It supports tocontrol access restrictions

based on login and password.

12.13 Advanced Features

Table 12.14 provide different advanced features related toeach software. All selected soft-

ware has long term leadership services except DoKS and SOPS.It is observed that all

software have proper support for their further development. CDS-Invenio at present sup-

port many advanced features such as providing citation data, providing virtual collection

support, page ranking support. CDS-Invenio also supports different personalization fea-

tures such as creating individual’s collection, generating discussion lists, writing reviews,

making different annoucements, ranking different digitalobjects available in the reposi-

tory. Similarly SOPS software supports to initiate discussion on particular digital docu-

ment available in the repository as well as allow to rank eachdigital document. DSpace &

DoKS software to some extent allow to create “My DSpace’ collections where individuals

can create their own collections and users can subscribe to aparticular collection.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS4

01

Table 12.14: Advanced Features

Advanced Fea-tures


Long TermLeadership

CDS-Invenio ismaintained anddeveloped byCERN hence ithas long termleadershipand consultingservices.

DSpace ismaintainedand developedby HP and MIT,it has long termleadership andservices.

DoKS hasnot broughtout any newversions after2006, henceit is difficult todemonstratelong termavailability ofDoKS.

EPrints ismaintainedand developedby University ofSouthampton.It has longterm lead-ership andconsultingservices.

Fedora ismaintainedand developedby CornellUniversity andUniversity ofVirginia Li-brary. It haslong termleadershipand consultingservices.

Greenstonehas long termleadershipand consultingservices as itis maintainedand developedby Universityof Waikato andsupported byUNESCO.

MyCoRe haslong term lead-ership andservices as itis supportedby HamburghUniversity,Germany.

SOPS hasnot broughtout any newversions afterits first re-lease henceit is difficult todemonstratelong termavailability ofSOPS.

Citation Data Software pro-vides citationdata featuresupport.

No No No No No Yes No

Road Map It has definedroadmap for fu-ture releases.

It has definedroadmap for fu-ture releases.

No No Yes Yes Yes No

Virtual Collec-tion Support

CDS-Inveniosupports gen-erating virtualcollectionsupport.

No No No No No No No

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS4

02

Advanced Fea-tures


Load Balanc-ing

It can handlelarge volumesof data andhas capacity tohandle morerequests at atime.

No mentionabout loadbalancingof DSpacefound any-where thoughDSpace canhandle millionsof documentscurrently norepositoryholds millionsof records.

No EPrints canperform wellif millionsof recordsare addedin EPrints ormore numberof people try toaccess EPrintsdatabase.

Fedora hasbeen tested byadding millionsof recordsand it hasperformed wellthough num-ber of usersaccessingdatabase aremore.

No No No

Visualization No No No No No No No NoPersonalization Software

supports per-sonalizatonfeature andeach user cancreate theirown collec-tion baskets.Users canalso generatediscussionon any doc-ument whichis available inthe repository.They can alsowrite reviewsof any docu-ment that areavailable in therepository.

DSpace sup-ports ’MyDSpace’ fea-ture which al-low end usersto subscribeto a particu-lar collectionand receiveupdates.

DoKS sup-ports to addsearcheddocumentsthrough DoKSrepository intoindividualsprofile.

No No No No Software sup-ports to createpersonal col-lections.

CH

AP

TE

R12.

CO

MP

AR

ATIV

EA

NA

LYS

IS4

03

Advanced Fea-tures


TranslationService


CommunityServices

Softwaresupports toprovide com-munity ser-vices such as itallow membersto exchangeideas, makeannoucementsand writereviews.

No No No No No No SOPS sup-ports to initiatediscussion ona particulardocumentavailable inSOPS repos-itory as wellas allow enduser to rateeach digitaldocument.

Page Ranking Software sup-ports pageranking algo-rithm for alldocumentsthat are addedinto the reposi-tory.

No No No No No No No


12.14 Digital Preservation

CDS-Invenio uses automatic conversion of any text file format to PDF format for the

possibility of long-term preservation of digital documents and future conversion. It uses

MARC 21 format to ensure portability and preservation. Software does not yet support

several other features related to digital preservation. There is no mention of any digital

preservation strategy. Software preserves file’s originalidentity such as its name and size.

It supports to upload compound digital objects for e.g. it can upload postscript files and can

automatically convert postscript files into pdf format. It also supports to upload multiple

file formats of the same document. It has facility to keep licensing conditions for individual

images/objects. CDS-Invenio can handle variety of file formats but does not yet support

file format versioning. Digital preservation in CDS-Invenio is supported to very limited

extent.

DSpace supports bit level preservation, where a digital file is preserved exactly as it was

created without any change. While submitting documents in DSpace system keeps track of

known bitstream formats and their support level. The repository provides a list of supported

file formats. Supported formats include those that are documented standards (e.g., TIFF,

AIFF, XML) or have published specifications (e.g., PDF, RIFF).

The other two categories of support for DSpace are "known" and "unsupported". "Known"

formats are those that are common enough to be familiar and usually quite popular, but

which are proprietary and there are no published specifications of those formats. "Unsup-

ported" formats are those that are either unknown to the Libraries or are extremely rare (e.

g., a compiled program, a commercial CAD/CAM file, etc.).

If the software supports a particular file format it shows thelist of supported file formats

else, if format is not supported by DSpace it will give a message “DSpace could not iden-

tify the format of this file. Please describe the format file inthe input box below the list”.

DSpace has built in data integrity check using MD5 (a messagedigest algorithm for secu-

rity applications) to ensure the correctness of each file. DSpace doesnot have any feature

to preserve pre-existing persistent identifiers for submitted digital objects. The provenance

information in DSpace consists of information such as submitted by, email of the submitter,

date, total number of bitstreams submitted, date of making document available on DSpace


web site, actual title of the file format uploaded, total bytes and checksum data. This data

is maintained in DC metadata.

DSpace has mechanisms to keep licensing conditions for eachindividual object as well as

software support to track and manage copyright and restriction issues. The software gen-

erates fixity data after submitting a file into the repositoryby the submitter. It is possible to

add new file formats into DSpace but they may not be supported by DSpace from preser-

vation point of view. DSpace can handle any type of MIME type of file format but may not

be able to preserve them if the format is not open standard.

DSpace version 1.4.2 does not support file format versioning. Software does not record

any representation information and system does not have anyway for automatic format

registration. While submitting any document into DSpace repository the software gives list

of DSpace supported file formats and if the particular file format is not in list it provides

option for the submitter to write details about the file format which is submitted by the

submitter.

EPrints at present does not support any digital preservation strategy but support some of

the features which would be required from digital preservation point of view and would be

useful in future. Software keeps file’s original identitiessuch as its name, size and created

date. Software supports checksum with MD5. EPrints version3 has introduced a new

’history’ function that documents all changes that are madeto records, from the point of

deposit onwards. This information will be useful in future,when there will be need to

modify the content of the repositories, e. g. to migrate file formats. To keep track of what

has happened to a record the repository will need to store both the object itself and all

actions that have been performed on it over time.

One of the important feature of EPrints is it preserves pre-existing persistent identifiers of

submitted digital objects. Software supports to link together compound digital objects and

supports to keep licensing conditions for individual digital objects in the repository with

different licensing conditions. EPrints uses MIME type identification of each file format,

but yet does not record any representation information of any file format added into the

repository.


Fedora at present does not support any preservation strategy but all objects added into

Fedora repository are Internally represented in the file system such as open XML format.

These XML files include data and metadata for the objects plusrelationships to services

and other objects.

Fedora does not preserve file’s original identity. It changes file’s name into the PID number

assigned by Fedora. Fedora supports variety of data integrity checks while file being added

into the repository such as MD5, SHA-1, SHA-256, SHA-384, SHA-512. Fedora sup-

ports to upload alternate ID’s or alternate URI of the digital documents if they are already

existing.

Fedora documents provenance information of each object that is added into the repository.

Software supports to upload compound digital objects whichis one of the unique feature

of Fedora and useful from digital preservation point of view. Fedora has ability to handle

variety of file formats and it does support file format versioning. Fedora uses Internet

MIME type for representing file formats and supports automatic format registration. For

unknown file formats system converts those files to Fedora supported MIME type formats

and uploads the documents.

Fedora supports audit trail features where it provies an essential technology for managing

the life cycle of the digital object. If the descriptive metadata of a digital object is changed

Fedora keeps two versions of the metadata. Software has digital signature feature support.

Fedora has been found more useful from digital preservationpoint of view.

The other software such as DoKS, Greenstone, MyCoRe, SOPS has not yet implemented

any digital preservation support.

Bibliography

[1] Witten, I. H. & Bainbridge, D. (2007). A retrospective look at Greenstone: lessons

from the first decade,JCDL'07, June 18-23, p.147-156.

407

Date post:	25-Apr-2018
Category:	Documents
Upload:	dinhhanh
View:	225 times
Download:	3 times

Chapter 12 Comparative Analysis of Software...

Documents