From amin.hedjazi at gmail.com Tue Dec 2 01:09:20 2008 From: amin.hedjazi at gmail.com (Amin Hedjazi) Date: Tue Dec 2 01:09:25 2008 Subject: [greenstone-devel] Plugin Developement Message-ID: <4105c9810812010409r164596ddxf4c77be57e8d06ac@mail.gmail.com> hi there does any boyd knows where i can fined some documents on greenstone plugin developements and the plugin programatical structures ? -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081201/5c2aad5e/attachment.html From vlado at etfbl.net Thu Dec 4 22:26:09 2008 From: vlado at etfbl.net (Vladimir Risojevic) Date: Thu Dec 4 22:24:29 2008 Subject: [greenstone-devel] cache_generated_images problem (and solution) Message-ID: <4937A231.8040406@etfbl.net> Dear Greenstone team, Since I am currently maintaining a few collections which consist mainly of scanned images, I welcome cache_generated_images option in Greenstone 2.81. However, when I tried to build a collection with cache_generated_images=true on a WinXP machine I got the following error messages: Use of uninitialized value in substitution (s///) at C:\Program Files\Greenstone/perllib/plugins/BaseMediaConverter.pm line 84. and **** Error is: fileparse(): need a valid pathname at C:\Program Files\Greenstone/perllib/plugins/BaseMediaConverter.pm line 88. I traced the problem to BaseMediaConverter.pm and found out that the first message appears because regexp in line 84 cannot match $base_dir because on windows $base_dir contains slashes as directory separators, while in $filename directory separators are backslashes. The second error message is merely a consequence of the first one, because $file is empty. In order to solve this either $base_dir or $filename has to be fixed. I couldn't find where $self->{'base_dir'} is set. It seems that it is not in line 67 of BaseMediaConverter.pm since $base_dir there is an empty string. In the end (and because it is very late night) I decided to use a quick and dirty approach and insert: $filename =~ s/\\/\//g; before the regexp in line 84 and fix the $filename. This solved the problem, and I hope it will be helpful to others. Maybe a better way to solve this problem would be to construct $self->{'base_dir'} with backslashes or slashes depending on the operating system, as utils::filename_cat does. However, as I said I cannot find where it is defined. Best regards, Vladimir -- Vladimir Risojevic Teaching Assistant Faculty of Electrical Engineering University of Banjaluka Patre 5 78000 Banjaluka Bosnia and Herzegovina Phone: +387 51 221 847, +387 51 221 876 Fax: +387 51 211 408 Email: vlado@etfbl.net WWW: http://www.etfbl.net From kjdon at cs.waikato.ac.nz Mon Dec 8 13:50:15 2008 From: kjdon at cs.waikato.ac.nz (Katherine Don) Date: Mon Dec 8 13:50:24 2008 Subject: [greenstone-devel] Fastcgi In-Reply-To: References: Message-ID: <493C6F47.5080500@cs.waikato.ac.nz> An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081208/c3dc75cd/attachment.html From kjdon at cs.waikato.ac.nz Mon Dec 8 14:16:53 2008 From: kjdon at cs.waikato.ac.nz (Katherine Don) Date: Mon Dec 8 14:17:02 2008 Subject: [greenstone-devel] Plugin Developement In-Reply-To: <4105c9810812010409r164596ddxf4c77be57e8d06ac@mail.gmail.com> References: <4105c9810812010409r164596ddxf4c77be57e8d06ac@mail.gmail.com> Message-ID: <493C7585.8050605@cs.waikato.ac.nz> An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081208/299dfb0b/attachment-0001.html From sklein at pratt.edu Tue Dec 9 03:14:30 2008 From: sklein at pratt.edu (Stephen I. Klein) Date: Tue Dec 9 03:14:01 2008 Subject: [greenstone-devel] RE: [greenstone-users] oaister In-Reply-To: <493C3ABF.2000506@cs.waikato.ac.nz> References: <003c01c95619$6ba1d970$42e58c50$@edu> <493C3ABF.2000506@cs.waikato.ac.nz> Message-ID: <004301c9593f$4994a5a0$dcbdf0e0$@edu> Katherine, Thank you for your comprehensive reply. I merely want to be able to: 1> produce an OAI compliant XML file with Greenstone, so I could indeed 2> Intermediate with a gateway (such as Los Alamos) and 3> harvest with OAIster. Previously, I performed step 1 with Luna and steps 2 and 3 as described. Does Greenstone produce OAI compliant XML files? Or can I export my Dublin Core from Greenstone to a XML file that is OAI compliant? Stephen Stephen I. Klein Electronic Resources/Systems Librarian Assistant Professor Pratt Institute Library 200 Willoughby Avenue Brooklyn, NY 11205 sklein@pratt.edu (718) 399 4423 Pratt From: Katherine Don [mailto:kjdon@cs.waikato.ac.nz] Sent: Sunday, December 07, 2008 04:06 PM To: Stephen I. Klein Cc: greenstone-users@list.scms.waikato.ac.nz; John Rose Subject: Re: [greenstone-users] oaister Hi Stephen I have just had a look on the web at OAIster and static repositories. Sorry, I should have done this before I replied to you the first time. After my 5 mins of reading, this is what I understand the situation is. Please correct me if I am wrong. OAIster harvests OAI repositories. To become a data provider, you need to check your repository against a validator, and then register. If you don't have a proper OAI server, then you can set up a static OAI repository, which is an XML file. These may be harvested by OAI repository gateways, which is what you are trying to do? Greenstone provides a proper OAI repository server (oaiserver), and from version 2.81 and later should validate against the repository validator specified on the OAIster "Steps to Becoming a Data Contributor" page. We currently don't provide exporting a collection as an OAI static repository. Is there a reason why you wish to keep using a static repository rather than setting up the proper OAI repository? Regards, Katherine Stephen I. Klein wrote: We are migrating our digital collections and need to keep our collection OAI harvestable. We currently have a presence via OAIster (http://oaister.umdl.umich.edu/o/oaister/) and have intermediated through the Los Alamos Gateway at: http://libtest.lanl.gov/ Does Greenstone allow for the building of OAI compliant XML files that are successfully intermediated via a standard gateway and harvestable with OAIster? The following page suggests the inverse: http://wiki.greenstone.org/wiki/index.php/OAI_support Any suggestions to approach this goal would be greatly appreciated. Thank you. Regards, Stephen I. Klein Electronic Resources/Systems Librarian Assistant Professor Pratt Institute Library 200 Willoughby Avenue Brooklyn, NY 11205 sklein@pratt.edu (718) 399 4423 Pratt _____ _______________________________________________ greenstone-users mailing list greenstone-users@list.scms.waikato.ac.nz https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081208/4e6db7dd/attachment.html From kjdon at cs.waikato.ac.nz Tue Dec 9 07:35:18 2008 From: kjdon at cs.waikato.ac.nz (Katherine Don) Date: Tue Dec 9 07:33:16 2008 Subject: [greenstone-devel] Re: [greenstone-users] oaister In-Reply-To: <004301c9593f$4994a5a0$dcbdf0e0$@edu> References: <003c01c95619$6ba1d970$42e58c50$@edu> <493C3ABF.2000506@cs.waikato.ac.nz> <004301c9593f$4994a5a0$dcbdf0e0$@edu> Message-ID: <493D68E6.4000001@cs.waikato.ac.nz> Hi Stephen No, Greenstone currently doesn't provide this option, as we provide a proper OAI repository (which you can use directly with OAIster). I have added a ticket to our trac bug/feature tracking system, so it may get added in the future. http://trac.greenstone.org/ticket/431 Regards, Katherine Stephen I. Klein wrote: > > > > Thank you for your comprehensive reply. > > > > I merely want to be able to: > > > > 1> produce an OAI compliant XML file with Greenstone, so I could > indeed > > 2> Intermediate with a gateway (such as Los Alamos) and > > 3> harvest with OAIster. > > > > Previously, I performed step 1 with Luna and steps 2 and 3 as described. > > > > Does Greenstone produce OAI compliant XML files? Or can I export my > Dublin Core from Greenstone to a XML file that is OAI compliant? > > > > Stephen > > > > > > > > Stephen I. Klein > Electronic Resources/Systems Librarian > Assistant Professor > Pratt Institute Library > 200 Willoughby Avenue > Brooklyn, NY 11205 > sklein@pratt.edu > (718) 399 4423 > *P**ra**t**t* > > > > *From:* Katherine Don [mailto:kjdon@cs.waikato.ac.nz] > *Sent:* Sunday, December 07, 2008 04:06 PM > *To:* Stephen I. Klein > *Cc:* greenstone-users@list.scms.waikato.ac.nz; John Rose > *Subject:* Re: [greenstone-users] oaister > > > > Hi Stephen > > I have just had a look on the web at OAIster and static repositories. > Sorry, I should have done this before I replied to you the first time. > > After my 5 mins of reading, this is what I understand the situation > is. Please correct me if I am wrong. > > OAIster harvests OAI repositories. To become a data provider, you need > to check your repository against a validator, and then register. > If you don't have a proper OAI server, then you can set up a static > OAI repository, which is an XML file. > These may be harvested by OAI repository gateways, which is what you > are trying to do? > > Greenstone provides a proper OAI repository server (oaiserver), and > from version 2.81 and later should validate against the repository > validator specified on the OAIster "Steps to Becoming a Data > Contributor" page. > > We currently don't provide exporting a collection as an OAI static > repository. > > Is there a reason why you wish to keep using a static repository > rather than setting up the proper OAI repository? > > Regards, > Katherine > > Stephen I. Klein wrote: > > We are migrating our digital collections and need to keep our collection OAI > harvestable. We currently have a presence via OAIster > (http://oaister.umdl.umich.edu/o/oaister/) and have intermediated through > the Los Alamos Gateway at: > > http://libtest.lanl.gov/ > > Does Greenstone allow for the building of OAI compliant XML files that are > successfully intermediated via a standard gateway and harvestable with > OAIster? > > The following page suggests the inverse: > > http://wiki.greenstone.org/wiki/index.php/OAI_support > > Any suggestions to approach this goal would be greatly appreciated. Thank > you. > > Regards, > > > Stephen I. Klein > Electronic Resources/Systems Librarian > Assistant Professor > Pratt Institute Library > 200 Willoughby Avenue > Brooklyn, NY 11205 > sklein@pratt.edu > (718) 399 4423 > Pratt > > > > > > > ------------------------------------------------------------------------ > > > > > _______________________________________________ > greenstone-users mailing list > greenstone-users@list.scms.waikato.ac.nz > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users > From amin.hedjazi at gmail.com Wed Dec 10 19:41:17 2008 From: amin.hedjazi at gmail.com (Amin Hedjazi) Date: Wed Dec 10 19:41:41 2008 Subject: [greenstone-devel] question about gsprintf Message-ID: <4105c9810812092241x531f08c5xda2b2b34bd682e3e@mail.gmail.com> hello every one can any body out there tell me what is the line 231 in file \gs2build\perllib\gsprintf.pm is good for ? i wanted to traslate the strings.properties inside \gs2build\perllib\ to persian but when i made a strings_fa.properties file like other traslations and saved it az utf-8 it returnd an error while trying to load the gli so i traced back the error and got to the line 231 in file \gs2build\perllib\gsprintf.pm and that wolude be the line below $linetext =~ s/(\s*)\#\s+Updated\s+(\d?\d-\D\D\D-\d\d\d\d)\s*$//i; becouse of this line my xml out put from the file downloadeinfo.pl wasent well formed and i got the error when i was trying to load the gli but when i commented out the line 231 in file \gs2build\perllib\gsprintf.pm my errors where gone and the gli loaded perfectly whit my traslations in there own palceses so sombody please tell me what is this line good for and if that problem was spose to be a bug shoulde i report it in the tracs ? tnx every one -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081210/ce85cc74/attachment.html From greenstone_team at cs.waikato.ac.nz Thu Dec 11 13:08:36 2008 From: greenstone_team at cs.waikato.ac.nz (Oran of Greenstone Team) Date: Thu Dec 11 13:08:54 2008 Subject: [greenstone-devel] Greenstone2.81rc2 released Message-ID: <49405A04.7070708@cs.waikato.ac.nz> Hello list members, We are pleased to announce that the Windows, GNU/Linux, Mac OS/X and Source distributions of Greenstone v2.81rc2 are now available for download from our sourceforge page: http://sourceforge.net/projects/greenstone or from http://www.greenstone.org/download Release notes are copied below. This release is further to the recent 2.81rc release (first advertised as 2.81). If you installed the 2.81rc release, we recommend you upgrade to 2.81rc2. This can be done in two ways: A) Simply install Greenstone2.81rc2 on top of the existing Greenstone2.81rc installation. This will overwrite all exising files with the updated files, but will not delete anything, so your collections will be preserved. Any changes to config files will be overwritten with the defaults. B) Rename the home folder of your existing Greenstone2.81rc installation by adding '.bak' to the folder name. Then install the new Greenstone2.81rc2 in its place and copy your collections and any modified config files from the old 2.81rc installation to the 2.81rc2 installation. As always, please report any problems or bugs to the mailing list. Regards, Oran and the rest of the Greenstone team. Release Name: 2.81rc2 The Windows, GNU/Linux, Mac OS/X and Source distributions of Greenstone v2.81rc2 are now available for download from our sourceforge page: http://sourceforge.net/projects/greenstone or via http://www.greenstone.org/download Important changes in this release include, in no particular order: Stability and Bug Fixes ----------------------- Some small problems in the recent 2.81rc release of Greenstone2 have been ironed out to create an overall more robust release. Some features have been restored (including realistic books and dynamic classifiers on Windows) and the LuceneWrapper.jar file has been put back into the release. GDBM ---- Greenstone now comes with it's own modified version of gdbm which can auto-detect the format of database files (ldb or bdb format) and load either format on any of Greenstone's supported platforms. This achieves a better level of portability for Greenstone collections, and allows collections built on one operating system to be served from other operating systems supported by Greenstone. Installer improvements ---------------------- * The new installer: - is now available in five languages - can now cope with being executed from a path with accented characters and other special characters. (There is still a known issue with chinese file paths, which can be avoided by simply running from c:\ or another path with no special characters.) * The source release is now provided as a platform-independent zip / tar archive * We now provide a simple binary zip / tar distribution for each platform Vista Compatibility ------------------- * When Greenstone is installed into the Program Files directory on Windows Vista, it is necessary to elevate to a higher access level to run GLI and the Greenstone server. As of this release, you can do this by launching the Start Menu items as an administrator. Just right-click the item and choose "Run as Administator", or set "Run as Adminsitrator" in the shortcut properties. Also, as a way to avoid having to elevate to higher access levels altogether, the default installation directory is now inside the current user's home folder. * Some Windows Vista users have experienced a problem when perl outputs warning messages in front of xml output passed to GLI. The error messages themselves are not fatal, but cause the xml to become invalid, resulting in a GLI crash. GLI has been modified to ignore these warning messages and thereby keep the validity of the xml. New Start Menu icons and server image ------------------------------------- Each item in a Greenstone Start Menu group is now has a unique icon so you can tell which is which at a glance. We have also added some links to the wiki and the Greenstone website for convenience. The old server image has also been replaced with the new GS2 Server logo. The release notes from the 2.81rc release and included below: Release Name: 2.81rc The Windows, GNU/Linux, Mac OS/X and Source distributions of Greenstone v2.81rc are now available for download from our sourceforge page: http://sourceforge.net/projects/greenstone or via http://www.greenstone.org/download Important changes in this release include, in no particular order: Installer: -------------- The Greenstone installer downloads are now created using only open source software, including Ant Installer (http://antinstaller.sourceforge.net/), Apache Ant (http://ant.apache.org/), our own search4j (based on launch4j http://launch4j.sourceforge.net/), and our own Greenstone release kits. We felt it was essential to move away from our existing, closed-source installer suite as it was not in the spirit of Greenstone to rely on proprietary software, and it invited the unnecessary cost of keeping the suite up-to-date. Using only open source software has also given us the freedom to customise the user experience of the installers. Where a feature was lacking in one of the open source packages, we have enjoyed the ability to "open the hood" and implement it. With the development of the Greenstone release kits we are now able to generate releases of Greenstone automatically and unattended. This process takes just 20 minutes, and it has helped us a lot in the development and testing of new features of Greenstone. We have been able to set up a feedback loop, where code committed one day is included in an automatic nightly snapshot release made available for download on our website the next day. Our users have also benefited from being able to obtain up-to-date snapshot releases of Greenstone in between our official releases. These daily snapshots are available through: http://www.greenstone.org/snapshots On Windows, the version number is included in the Start Menu which means that multiple installations of Greenstone will have their own entries in the Start Menu. The installer no longer writes to the registry, so installation no longer requires administrator privileges. ImageMagick is now bundled with Greenstone for binary web releases for all platforms (previously it was only provided on a CD-ROM release) and includes JPEG2000 support. The installer offers the option to install this or not. You can skip installing it if you already have ImageMagick previously installed. Ghostscript is now bundled with Greenstone for binary web releases for Windows and Mac. The installer offers the option to install this or not. You can skip installing it if you already have Ghostscript previously installed. Importing and Plugin Changes: ------------------------------ Plugin Restructuring: The plugins have been restructured. This has been done mostly for coding efficiency. The most noticeable change is that plugins have been renamed. xxxPlug now becomes xxxPlugin, and some have also had their names modified or expanded to be clearer. For example, DBPlug is now DatabasePlugin, PPTPlug is PowerPointPlugin. The complete list of new plugins can be seen at http://wiki.greenstone.org/wiki/index.php/Plugins. Old collections should still build okay in GLI, which will map the old plugin names to the new ones. Command line building should also work, but the configuration file won't be altered to use the new names. A lot of work has been done trying to get Greenstone to work properly with non-ascii filenames. Two versions of the filename are stored, [Source] for displaying the filename, and [SourceFile] for linking to the file from a web page. The -smart_block option (most commonly seen with HTMLPlugin) has been deprecated . Instead we have a first pass through the documents to find out which ones should be blocked. MARCPlugin and MARCXMLPlugin can now map metadata to Qualified Dublin Core as well as Dublin Core. MARCXMLPlugin now assigns metadata from metadata.xml files. EMAILPlugin now saves binary attachments as binary files on Windows ImagePlugin and PagedImagePlugin now offer the -cache_generated_images option to prevent thumbnails and screenview images being recreated each import. OAIPlugin saves the metadata as Dublin Core rather than moving it all to the ex metadata set. This means that it won't show up in the GLI unless the files are exploded. Exploding is now available for OAI records. ProCitePlugin no longer uses the pc namespace. Metadata is stored using the field names set in the workform definition, rather than using Field1Name and Field1Value etc.. -reversesort option to import.pl to be used with -sortmeta option to sort in reverse order. Tidied up OID generation. OIDtype and OIDmetadata options are now available for each plugin as well as globally from import.pl. Hashing usually occurs on the original file, but some plugins specify that hashing should be done on the Greenstone XML document. Building and Indexing Changes: ------------------------------- Improvements to Lucene incremental building. Lucene document identifiers now match Greenstone identifiers, rather than 1, 2, 3, thanks to DL Consulting. This improves search efficiency, and is another step towards true incremental building. Rebuilding with no new documents shouldn't break the index. MGPP and Lucene building tidied up. 'allfields' now means combined searching over all specified indexes (not all document metadata) for both mgpp and lucene. 'metadata' will index all metadata, but no longer reindexes metadata that has already been specified. MGPP indexing over combined fields now works properly. New collection configuration file option: infodbtype. Values include gdbm (the default), gdbm-txtgz, sqlite, mssql. This specifies what database system to use for the collection metadata database. Currently this needs to be added to collect.cfg by hand, as it is not available in GLI yet. gdbm: the default, and is what has always been used previously. This is platform dependent. It transfers between Windows and Linux, but not to/from a Mac. gdbm-txtgz: A gzipped text version of the database. At runtime, the first time this collection is accessed, it will be unpacked and converted to the appropriate GDBM database using txt2db. This is a good choice if you are creating a collection to be used on another operating system, especially if one or more of those operating systems is a Mac. sqlite: Platform independent database using SQLite. The new dynamic classifiers can be used with this database. Thanks to DL Consulting. mssql: Windows specific database using MS SQL Server. See http://wiki.greenstone.org/wiki/index.php/Using_MSSQL_for_Collection_Database for information about how to set this up. The new dynamic classifiers can be used with this database. Thanks to DL Consulting. Depositor: ------------ Collection editing using the Depositor is now enabled by default for the admin user. The metadata fields offered for each document can now easily be customised from the GLI. By default, the depositor will import and build each document into the collection when it is added. It can now be easily set up to just "deposit" the item without rebuilding. See http://wiki.greenstone.org/wiki/index.php/How_to_use_the_depositor for more information. GLI ------- A new right-click file option for binary files that go through a conversion process to be imported, such as PDF, Word and PowerPoint files. "Replace source document with HTML" will convert the original file to HTML and replace it in the collection. This means that the converted HTML (which may be unattractive) can now be modified in the collection. This is available for Remote GLI too. A new right-click file option on the collection tree background to refresh the file view. This is useful if you have manually added files to the collection outside of GLI. MetadataXMLPlugin has been moved 'below the line' in the Plugins panel so cannot be removed in GLI. If you are using GLI to add metadata, then you need this plugin. The Export As option now only exports one collection at a time. Collections can be exported as GreenstoneMETS, FedoraMETS, MARCXML and DSpace archive. 'NavigationBar pulldown' added to the list of format options - this makes the navigation 'bar' a drop down list instead of a bar across the page. Lots of work done on making the Download panel work better, including getting download processes to terminate when they are cancelled or when GLI is closed while they are still running. New panel under the Format tab, "Depositor Metadata" which allows customisation of which metadata fields should be offered in the depositor for that collection. CJK segmentation option has been added to GLI. This doesn't do proper word segmentation, but adds a space in between each CJK character. The character ranges have been expanded to work with Japanese and Korean. It is applied to metadata as well as document text. Another new feature in Greenstone v2.81 is the ability to schedule the automatic rebuilding of a greenstone collection using the GLI. There's a new panel under the Create tab allowing the scheduling of automatic collection rebuilding. Scheduling will require some configuration in order for it to work. The following link has more information on how to do this for each platform: http://wiki.greenstone.org/wiki/index.php/Scheduled_Collection_Building_from_the_Librarian_Interface Greenstone Runtime: ---------------------- New dynamic classifiers (if the collection uses sqlite or MSSQL as the collection database). These are generated at runtime so do not require the collection to be rebuilt for classifier changes. Another step towards true incremental building. See http://wiki.greenstone.org/wiki/index.php/More_about_classifiers#How_do_I_use_dynamic_classifiers.3F for more information. Thanks to DL Consulting. Large code restructuring. Code is split between common-src, build-src and runtime-src. Makes it easer to use code in other projets, such as Greenstone 3 and running Greenstone on an iPhone/iPod Touch. External links now default to going straight to the web page, rather than showing a warning page first. Improvements to the oaiserver, thanks to DL Consulting. Resumption token support has been added, and it now validates against online validation tools. Greenstone now compiles for Linux on 64-bit platforms. All programs are compiled natively for 64-bit, except for those that rely on mg/mgpp, which still need to be 32-bit compiled. As part of the configure/make process, the correct flags are automatically set, so from the developers point of view you compile up Greenstone on a 64-bit machine the exact same way you do for any other Unix-based system. Greenstone should now compile with Microsoft Visual Studio 2005, thanks to DL Consulting. FLI - Fedora Librarian Interface --------------------------------- The Fedora Librarian Interface (FLI) is very much like GLI in that it allows you to gather together your documents. It then uses Greenstone's ability to convert documents into the FedoraMETS format so that these can be ingested (put into) a Fedora repository. The process of building a collection using FLI exports documents into a repository maintained by a Fedora server rather than one maintained by Greenstone. In order to use FLI, you will need to have Fedora installed. More information on how to install Fedora and set it up to work with FLI, and how to run FLI itself, can be found in the documents: 1. Installing Fedora (2.2.1/3.0) and Fedora-related information http://wiki.greenstone.org/wiki/index.php/InstallingFedora 2. Installing Fedora Generic Search (to provide full-text indexing and searching capabilities for a Fedora repository) http://wiki.greenstone.org/wiki/index.php/InstallingFedoraGSearch 3. Running FLI, the Fedora Librarian Interface http://wiki.greenstone.org/wiki/index.php/RunningFLI Translations: -------------- Thanks to: John Rose, for help with English GLI help, French translations for GLI and Greenstone. Maxime Rouast for Greenstone French translations Celine Guimbertaud for GLI French translations Yohannes Mulugeta and Abiyot Bayou for Greenstone Amharic translations Kamal Salih for GLI Arabic translations Gerhard Riesthuis for Greenstone Dutch translations Mohan Raj Pradhan for GLI Nepali translations. Diego Spano for translating the installer's interface into Spanish. Xiaofeng Yu for translating the installer's interface into Mandarin. Doris Jung for translating the installer's interface into German. ...and many other minor improvements and bug fixes We want to ensure that Greenstone works well for you. Please report any problems to the Greenstone mailing list greenstone-users@list.scms.waikato.ac.nz. [DL Consulting (http://www.dlconsulting.com) are the world's leading suppliers of commercial consulting, customization, support, maintenance and hosting services for the Greenstone digital library software suite.] From anu at ncsi.iisc.ernet.in Mon Dec 1 20:33:38 2008 From: anu at ncsi.iisc.ernet.in (K.T Anuradha) Date: Thu Dec 11 22:24:07 2008 Subject: [greenstone-devel] Multilingual database creation: Lab exercises In-Reply-To: <492B8158.1000907@cs.waikato.ac.nz> References: <492B8158.1000907@cs.waikato.ac.nz> Message-ID: Dear Greenstone user, I wanted to share lab exercise which I had prepared for a workshop I conducted during December 2008 on Multilingual capability on GSDL. Hope it is of use to all those working on multilingual feature! Regards, Anuradha -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- A non-text attachment was scrubbed... Name: multilingual.pdf Type: application/pdf Size: 111593 bytes Desc: Url : https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081201/25fd8cac/multilingual-0001.pdf From boroday_katya at yahoo.com Thu Dec 11 01:01:46 2008 From: boroday_katya at yahoo.com (Katya Boroday) Date: Thu Dec 11 22:24:08 2008 Subject: [greenstone-devel] Technical question Message-ID: <407437.74551.qm@web55406.mail.re4.yahoo.com> The Tatarstan Center of the Scientific and Technical Information would like to use the on-line version of Greenstone's digital libraries in our work. Unfortunately, we can't install the necessary software because of the some technical reasons. Please, help us to solve this problem.   Looking forward to hear from you, Boroday Katya Russia, Kazan ________________________________________________________ ?? ??? ? Yahoo!? ????????? ??????????? ? ??????????. Yahoo! ?????! http://ru.mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081210/bd928d04/attachment.html From ybakelli at hotmail.com Sat Dec 13 10:58:30 2008 From: ybakelli at hotmail.com (Bakelli Yahia) Date: Sat Dec 13 10:58:43 2008 Subject: [greenstone-devel] Multilingual database creation: Lab exercises In-Reply-To: References: <492B8158.1000907@cs.waikato.ac.nz> Message-ID: unsubscribe _________________________________________________________________ Lancez des recherches en toute sécurité depuis n'importe quelle page Web. Téléchargez GRATUITEMENT Windows Live Toolbar aujourd'hui ! http://toolbar.live.com -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081212/d9fcf047/attachment.html From ybakelli at hotmail.com Sat Dec 13 10:58:46 2008 From: ybakelli at hotmail.com (Bakelli Yahia) Date: Sat Dec 13 10:58:59 2008 Subject: [greenstone-devel] unsubscribe In-Reply-To: References: <492B8158.1000907@cs.waikato.ac.nz> Message-ID: unsubscribe _________________________________________________________________ Lancez des recherches en toute sécurité depuis n'importe quelle page Web. Téléchargez GRATUITEMENT Windows Live Toolbar aujourd'hui ! http://toolbar.live.com -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081212/00008d88/attachment.html From amin.hedjazi at gmail.com Sat Dec 13 18:39:13 2008 From: amin.hedjazi at gmail.com (Amin Hedjazi) Date: Sat Dec 13 18:39:24 2008 Subject: [greenstone-devel] question about gsprintf,please help me Message-ID: <4105c9810812122139y7e9ea093q4ba0af2705057e9f@mail.gmail.com> hello every one can any body out there tell me what is the line 231 in file \gs2build\perllib\gsprintf.pm is good for ? i wanted to traslate the strings.properties inside \gs2build\perllib\ to persian but when i made a strings_fa.properties file like other traslations and saved it az utf-8 it returnd an error while trying to load the gli so i traced back the error and got to the line 231 in file \gs2build\perllib\gsprintf.pm and that wolude be the line below $linetext =~ s/(\s*)\#\s+Updated\s+(\d?\d-\D\D\D-\d\d\d\d)\s*$//i; becouse of this line my xml out put from the file downloadeinfo.pl wasent well formed and i got the error when i was trying to load the gli but when i commented out the line 231 in file \gs2build\perllib\gsprintf.pm my errors where gone and the gli loaded perfectly whit my traslations in there own palceses so sombody please tell me what is this line good for and it apears this line was making my utf-8 code to have some syntax error in it !!!!! if that problem was spose to be a bug shoulde i report it in the tracs ? please help me tnx every one -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081213/e8e8baaf/attachment.html From amin.hedjazi at gmail.com Mon Dec 15 20:53:33 2008 From: amin.hedjazi at gmail.com (Amin Hedjazi) Date: Mon Dec 15 20:53:39 2008 Subject: [greenstone-devel] Persian Translation Updates and some Questions about the release process Message-ID: <4105c9810812142353r165fa7excdf21116f001549c@mail.gmail.com> hello ,again ive just updated the falowing tickets in the trac and updated the falowing translation files: Ticket #405 Ticket #416 and the updated files are these : CrossCollectionSearch_fa.properties GS2Construct_fa.properties GS2LuceneSearch_fa.properties interface_default_fa.properties IViaSearch_fa.properties message_fa.properties Visualizer_fa.properties AbstractBrowse_fa.properties AbstractGS2FieldSearch_fa.properties AbstractSearch_fa.properties Authentication_fa.properties in Ticket #416 dictionary_fa.properties in Ticket #405 would some one be so kined and letting me know that how are the files uploaded are processed? would they be added in the next releases ? and if so would some one notify me if any of my files that i have uploaded needed some changes to be able to be added in next releases ? and that who is responsible for cheking them out ? what happens if these files were rejected ? i am going to upload the gli orientation fixes for right to left languages next please let me ok and is it possible to have contact with greenstone teem directly to be more informed about the releases ? many thanx for your supports Amin From qq6 at cs.waikato.ac.nz Tue Dec 16 08:42:35 2008 From: qq6 at cs.waikato.ac.nz (qq6@cs.waikato.ac.nz) Date: Tue Dec 16 08:42:44 2008 Subject: [greenstone-devel] unsubscribe In-Reply-To: References: <492B8158.1000907@cs.waikato.ac.nz> Message-ID: <64877.206.207.225.23.1229370155.squirrel@webmail.scms.waikato.ac.nz> Hi To unsubscribe from the greenstone-devel mailing list, please go to https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel, enter your e-mail address in the last box near the bottom of the page, and click "Unsubscribe or edit options". Regards Quan > > unsubscribe > _________________________________________________________________ > Lancez des recherches en toute sécurité depuis n'importe quelle page Web. > Téléchargez GRATUITEMENT Windows Live Toolbar aujourd'hui ! > http://toolbar.live.com_______________________________________________ > greenstone-devel mailing list > greenstone-devel@list.scms.waikato.ac.nz > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel > From qq6 at cs.waikato.ac.nz Tue Dec 16 10:24:00 2008 From: qq6 at cs.waikato.ac.nz (qq6@cs.waikato.ac.nz) Date: Tue Dec 16 10:24:12 2008 Subject: [greenstone-devel] Persian Translation Updates and some Questions about the release process In-Reply-To: <4105c9810812142353r165fa7excdf21116f001549c@mail.gmail.com> References: <4105c9810812142353r165fa7excdf21116f001549c@mail.gmail.com> Message-ID: <54404.206.207.225.23.1229376240.squirrel@webmail.scms.waikato.ac.nz> Hi Amin Please read http://wiki.greenstone.org/wiki/index.php/Information_for_language_maintainers for the details. Regards Quan > hello ,again > ive just updated the falowing tickets in the trac and updated the > falowing translation files: > > Ticket #405 > Ticket #416 > > and the updated files are these : > > CrossCollectionSearch_fa.properties > GS2Construct_fa.properties > GS2LuceneSearch_fa.properties > interface_default_fa.properties > IViaSearch_fa.properties > message_fa.properties > Visualizer_fa.properties > AbstractBrowse_fa.properties > AbstractGS2FieldSearch_fa.properties > AbstractSearch_fa.properties > Authentication_fa.properties > in Ticket #416 > > dictionary_fa.properties > in Ticket #405 > > would some one be so kined and letting me know that how are the files > uploaded are processed? > would they be added in the next releases ? > > and if so > > would some one notify me if any of my files that i have uploaded > needed some changes to be able to be added in next releases ? > > and that who is responsible for cheking them out ? > what happens if these files were rejected ? > > i am going to upload the gli orientation fixes for right to left languages > next > > please let me ok > and is it possible to have contact with greenstone teem directly to be > more informed about the releases ? > > many thanx for your supports > Amin > > _______________________________________________ > greenstone-devel mailing list > greenstone-devel@list.scms.waikato.ac.nz > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel > From qq6 at cs.waikato.ac.nz Tue Dec 16 10:30:36 2008 From: qq6 at cs.waikato.ac.nz (qq6@cs.waikato.ac.nz) Date: Tue Dec 16 10:30:45 2008 Subject: [greenstone-devel] Technical question In-Reply-To: <407437.74551.qm@web55406.mail.re4.yahoo.com> References: <407437.74551.qm@web55406.mail.re4.yahoo.com> Message-ID: <57507.206.207.225.23.1229376636.squirrel@webmail.scms.waikato.ac.nz> Hi If you want to install a binary Greenstone, please go to http://www.greenstone.org/download#snapshots-dist to dowmload the source. If you want to install a Greenstone from the SVN repository, please read http://wiki.greenstone.org/wiki/index.php/Install_GSDL_from_SVN_in_Linux for the details. Regards Quan > The Tatarstan Center of the Scientific and Technical Information would > like to use the on-line version of Greenstone's digital libraries in our > work. Unfortunately, we can't install the necessary software because of > the some technical reasons. Please, help us to solve this problem. >   > Looking forward to hear from you, Boroday Katya > Russia, Kazan > > > ________________________________________________________ > Ð’Ñ‹ уже Ñ Yahoo!? > ИÑпытайте обновленную и улучшенную. Yahoo! > Почту! > http://ru.mail.yahoo.com_______________________________________________ > greenstone-devel mailing list > greenstone-devel@list.scms.waikato.ac.nz > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel > From greenstone_team at cs.waikato.ac.nz Tue Dec 16 18:58:09 2008 From: greenstone_team at cs.waikato.ac.nz (Anupama of Greenstone Team) Date: Tue Dec 16 18:58:19 2008 Subject: [greenstone-devel] Re: [greenstone-users] Regarding Greenstone In-Reply-To: <1228906641.05d0abb9a864ae4981e933685b8b915c@mail.in.com> References: <1228906641.05d0abb9a864ae4981e933685b8b915c@mail.in.com> Message-ID: <49474371.80202@cs.waikato.ac.nz> Hello Jayanta, In addition to Suresh Nair's suggestion of visiting www.greenstone.org: > Is it developed in Java ? If it is then I would like to join the > community, since I am a Java developer I can try for it. > There fore, I would like to request you to give me some detail about the > project and the language in which it is developed. - The Greenstone 2 server's code is in C++. - The Greenstone 3 server's code is in Java. Greenstone 3 is the research version and does nearly all things that Greenstone 2 does plus a few more. - The Greenstone Librarian Interface used by both Greenstone 2 and Greenstone 3 is in Java. - The importing and building scripts, as well as the plugins they use to build the collections are written in Perl. The scripts can be called from the command line but are also invoked by GLI. Regards, Anupama Jayanta Bora wrote: > Dear Sir, > > I am Jayanta from Delhi, India. I am a Software Engineer and working in > the field of Java/J2EE. > > I am interested to know about greenstone project and I would like to > join the development community which will help me to expand my knowledge > and skill. > > I tried to know about the project and come to know that its a very good > project for digital library. > > Is it developed in Java ? If it is then I would like to join the > community, since I am a Java developer I can try for it. > > There fore, I would like to request you to give me some detail about the > project and the language in which it is developed. > > > Regards, > > Jayanta > > > > Get Yourself a cool, short *@in.com* Email ID now! > rce=invite&utm_medium=outgoing> > > > ------------------------------------------------------------------------ > > _______________________________________________ > greenstone-users mailing list > greenstone-users@list.scms.waikato.ac.nz > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users From greenstone_team at cs.waikato.ac.nz Wed Dec 17 18:34:05 2008 From: greenstone_team at cs.waikato.ac.nz (Anupama of Greenstone Team) Date: Wed Dec 17 18:34:16 2008 Subject: [greenstone-devel] Re: [greenstone-users] Microsoft Office 2007 revisited Message-ID: <49488F4D.2000809@cs.waikato.ac.nz> Forwarding a copy to the mailing list: Hello Doug, The ticket number 426 at Trac has not been updated to reflect the Greenstone Team's more recent discussions on the topic. It seems likely that we will be trying to use Open Office as an alternative means of converting various documents--particularly the different kinds of MS Office documents, such as .docx, ppt--where this is installed, else we may default to using the current conversion tools. You are right that a plugin to handle Open Office documents is also a requirement. Our present thinking at this stage is not to parse the docx or other MS Office formats ourselves, but to rather use Open Office's ability to convert them. Similarly, we might try to use Open Office itself to convert Open Office documents or otherwise fall back on the OpenDocument plugin (see below). Your intention in writing a plugin for OOXML sounds like it might not require Open Office to be installed in order to accomplish the conversion to HTML, is that right? It does sound very helpful. > I haven't dug into the OpenDocument plugin, At present, the OpenDocumentPlugin.pm seems to extract only the text from the document, going by what the starting comments say: # Processes OASIS Open Document format. # Word processing document: .odt, template: .ott # Spreadsheet document: .ods, template: .ots # Presentation document: .odp, template: .otp # Graphics document: .odg, template: .otg # Formulas document: .odf, template: .otf (not supported) #This basically extracts any text out of the document, but not much else. # this inherits ReadXMLFile, and therefore offers -xslt option, but does # nothing with it. Regards, Anupama Doug Carter wrote: > Hi all, > > Can anyone give me a rough development status on this? All of the > converters mentioned on "http://trac.greenstone.org/ticket/426" are > deficient in one way or another. Plus most of them are concerned only > with docx and not the whole OOXML family of documents. > > I noticed that you've already got an OpenDocument plugin available. > This may be an ignorant question, but isn't the framework of a ODT > similar to OOXML? (a zip file with some xml/images) > > I haven't dug into the OpenDocument plugin, but I'm wondering why it > wouldn't be a good starting place to develop a OOXML plugin. > Before I get too far looking into this, I'd like to know if someone > is already working on it. I don't want to duplicate the effort. > > Thanks, > > Doug > > > On Thu, Dec 04, 2008 at 06:52:10PM -0800, Jeff Crump wrote: >> Another message from Greenstone, with a link to the converter "to do" >> ticket. There are lots of potential conversion tools in the ticket >> report. They are open to our input on the tools (and I guessing you may >> have already made determinations on some of them). >> >> Best, >> Jeff >> -----Original Message----- >> From: Anupama of Greenstone Team >> [mailto:greenstone_team@cs.waikato.ac.nz] Sent: Thursday, December 04, 2008 6:39 PM >> To: Jeff Crump; Katherine Don >> Subject: Re: [greenstone-users] Microsoft Office 2007 revisited >> >> Hello Jeff, >> >> > Is this a matter of finding a pre-existing converter that works with >>> Office 2007, or writing it yourselves? >> It is indeed a matter of finding a pre-existing open-source converter >> tool and embedding it into Greenstone's building workflow by wrapping it >> in a plugin. >> >> I have added a "To Do" ticket for this, as intimated (see >> http://trac.greenstone.org/ticket/426), but will ask whether we can >> expedite our looking into this matter. There are many people using >> Office documents who want Greenstone to be compatible with the more >> recent formats. It is certainly the only way to proceed. >> >> The filed ticket has some links to conversion tools for us to consider. Is there any *open-source* tool that you may know of in your experience >> and which you prefer for its ability to accurately accomplish the >> conversion? If so, we can give it preference when we consider which one >> to incorporate. If you do not know of any, don't worry. >> >> Thanks for your valuable input, >> Anupama >> >> >> >> >> Jeff Crump wrote: >>> Hi Anupama, >>> Thank you VERY much for clarifying this! I asked my original question >> badly. Without the ability to convert Office 2007 to html and make it >> searchable full-text, we would have no reason to upgrade from 2.52. >>> I'm afraid our organization will soon be upgrading entirely to Office >> 2007. Our Greenstone Digital Library is actually our organization's main >> document repository - documents go in and out each day (we rebuild the >> library every night), so it isn't really an option for us to have be >> unable to convert Office 2007. >>> Is this a matter of finding a pre-existing converter that works with >> Office 2007, or writing it yourselves? >>> Thanks and best regards, >>> Jeff >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -----Original Message----- >>> From: Anupama of Greenstone Team [mailto:greenstone_team@cs.waikato.ac.nz] >>> Sent: Wednesday, December 03, 2008 6:17 PM >>> To: Jeff Crump >>> Subject: Re: [greenstone-users] Microsoft Office 2007 revisited >>> >>> Hello Jeff, >>> Greenstone at present is still using the wvWare tool to convert MS >> Word documents to html. It is not able to handle the more recent Word >> formats. >>> We intend to look into alternative conversion tools both for Word and >> other MS Office formats. I'll add in a "To Do" ticket about this. >>> Thanks, >>> Anupama >>> >>> Jeff Crump wrote: >>>> Hi, We're on Greenstone 2.52. We are considering an upgrade to 2.8x >> but our main requirement is that Microsoft Office 2007 documents build >> properly. >>>> I was told on this list to try 2.8, but we can't find any >> documentation anywhere saying that Office 2007 (Word, Excel, Powerpoint, >> etc.) is supported in 2.8. >>>> Can anyone point me to this documentation? Or can anyone verify from >> experience that Office 2007 documents are supported in Greenstone 2.8 or >> 2.81? >>>> If all we need is the right plugin, rather than the full upgrade, >> that would be great to know, too. >>>> Thanks again, >>>> Jeff >>>> >>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> - >>>> -- >>>> >>>> _______________________________________________ >>>> greenstone-users mailing list >>>> greenstone-users@list.scms.waikato.ac.nz >>>> https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users >>> > From greenstone_team at cs.waikato.ac.nz Wed Dec 17 18:46:45 2008 From: greenstone_team at cs.waikato.ac.nz (Anupama of Greenstone Team) Date: Wed Dec 17 18:46:55 2008 Subject: [greenstone-devel] Technical question In-Reply-To: <407437.74551.qm@web55406.mail.re4.yahoo.com> References: <407437.74551.qm@web55406.mail.re4.yahoo.com> Message-ID: <49489245.5010605@cs.waikato.ac.nz> Hello Katya, 1. Can you tell us what version of Greenstone you were trying to install? For instance, was it the recent Greenstone 2.81 rc2? 2. What is the operating system you are trying to install it on? Windows, Linux or a Mac OS? And which version of the OS are you running? Is there any other specific environment information which you think it will be useful for us to know about? Do also try the links to the latest binaries (nightly snapshots) that Quan (qq6) provided. 3. If you would rather try to install Greenstone from its source code, there are some additional links related to what Quan provided on the page http://wiki.greenstone.org/wiki/index.php/Installing_Greenstone All the best, Anupama Katya Boroday wrote: > The Tatarstan Center of the Scientific and Technical Information would > like to use the on-line version of Greenstone's digital libraries in our > work. Unfortunately, we can't install the necessary software because of > the some technical reasons. Please, help us to solve this problem. > > Looking forward to hear from you, Boroday Katya > Russia, Kazan > > > ------------------------------------------------------------------------ > > ?? ??? ? Yahoo!? ????????? ??????????? ? ??????????. Yahoo! ????? > ! > > > ------------------------------------------------------------------------ > > _______________________________________________ > greenstone-devel mailing list > greenstone-devel@list.scms.waikato.ac.nz > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel From stefan.flo at gmail.com Wed Dec 17 22:30:56 2008 From: stefan.flo at gmail.com (Stefan Florin) Date: Wed Dec 17 22:39:20 2008 Subject: [greenstone-devel] Question Message-ID: <2a11c1db0812170130p3a247fabsc49468c6ce1df660@mail.gmail.com> Hello, My Name is Stefan Florin, I've installed Greenstone and have some problems in managing access database files. I've created a .dbi file but I get an error when trying to build the Collection (I'm using the demo Greenstone collection). Any help will be appreciated. Thank you. #!c:\strawberry\perl\bin\perl.exe ## ## printenv -- demo CGI program which just prints its environment ## use POSIX; use strict; use CGI qw(:standard); use CGI::Carp qw(fatalsToBrowser); use DBI; use Time::Local print header; $dbplug_debug=1; ###################################### ## Set DSN-Less Connection ###################################### my $DSN = 'driver=Microsoft Access Driver (*.mdb);dbq=c:\Documents and Settings\fstefan\Greenstone2\collect\demo\test.mdb'; my $dbh = DBI->connect("dbi:ADO:$DSN", '','') or die "$DBI::errstr\n"; ###################################### ## Generate the SQL Statement ###################################### my $sql = qq{ SELECT * FROM tblContacts }; my $sth = $dbh->prepare( $sql ); $sth->execute() or die "Execution problem: $DBI::errstr"; my( $id, $lastname, $firstname); $sth->bind_columns( undef, \$id, \$lastname, \$firstname); while( $sth->fetch() ) { print "$id, $lastname, $firstname" ."
"; } %db_to_greenstone_fields = ( "firstName" => "Title", "lastName" => "text" ); ####################################### ## Close Connection ####################################### $dbh->disconnect; -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081217/3ea13313/attachment.html From greenstone_team at cs.waikato.ac.nz Thu Dec 18 14:49:04 2008 From: greenstone_team at cs.waikato.ac.nz (Katherine of Greenstone Team) Date: Thu Dec 18 14:49:15 2008 Subject: [greenstone-devel] Persian Translation Updates and some Question about the release process In-Reply-To: <4105c9810812142353r165fa7excdf21116f001549c@mail.gmail.com> References: <4105c9810812142353r165fa7excdf21116f001549c@mail.gmail.com> Message-ID: <4949AC10.6070800@cs.waikato.ac.nz> An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081218/11bfa116/attachment.html From kjdon at cs.waikato.ac.nz Fri Dec 19 09:31:49 2008 From: kjdon at cs.waikato.ac.nz (Katherine Don) Date: Fri Dec 19 09:32:01 2008 Subject: [greenstone-devel] Question In-Reply-To: <2a11c1db0812170130p3a247fabsc49468c6ce1df660@mail.gmail.com> References: <2a11c1db0812170130p3a247fabsc49468c6ce1df660@mail.gmail.com> Message-ID: <494AB335.7030809@cs.waikato.ac.nz> Hi Stefan What are you trying to do exactly? You don't need a dbi file to build the demo collection. You can just run the Librarian Interface, open the demo collection (File->Open), then go to the Create tab and click build collection. Regards, Katherine Stefan Florin wrote: > Hello, > > My Name is Stefan Florin, I've installed Greenstone and have some > problems in managing access database files. I've created a .dbi file > but I get an error when trying to build the Collection (I'm using the > demo Greenstone collection). Any help will be appreciated. Thank you. > > > #!c:\strawberry\perl\bin\perl.exe > ## > ## printenv -- demo CGI program which just prints its environment > ## > use POSIX; > use strict; > use CGI qw(:standard); > use CGI::Carp qw(fatalsToBrowser); > use DBI; > use Time::Local > print header; > > > > $dbplug_debug=1; > > ###################################### > ## Set DSN-Less Connection > ###################################### > my $DSN = 'driver=Microsoft Access Driver (*.mdb);dbq=c:\Documents and > Settings\fstefan\Greenstone2\collect\demo\test.mdb'; > my $dbh = DBI->connect("dbi:ADO:$DSN", '','') > or die "$DBI::errstr\n"; > > ###################################### > ## Generate the SQL Statement > ###################################### > my $sql = qq{ SELECT * FROM tblContacts }; > my $sth = $dbh->prepare( $sql ); > > $sth->execute() or die "Execution problem: $DBI::errstr"; > > my( $id, $lastname, $firstname); > $sth->bind_columns( undef, \$id, \$lastname, \$firstname); > > while( $sth->fetch() ) { > print "$id, $lastname, $firstname" ."
"; > } > > %db_to_greenstone_fields = ( > "firstName" => "Title", > "lastName" => "text" > ); > > ####################################### > ## Close Connection > ####################################### > $dbh->disconnect; > > > ------------------------------------------------------------------------ > > _______________________________________________ > greenstone-devel mailing list > greenstone-devel@list.scms.waikato.ac.nz > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel > From oranfry at cs.waikato.ac.nz Fri Dec 19 17:28:12 2008 From: oranfry at cs.waikato.ac.nz (Oran Fry) Date: Fri Dec 19 17:28:28 2008 Subject: [greenstone-devel] Final of Greenstone2.81 Released Message-ID: <494B22DC.9010801@cs.waikato.ac.nz> Hello Users and Developers of Greenstone, We are pleased to announce that the Windows, GNU/Linux, MacOS and Source distributions of the finalised Greenstone2.81 are now available for download from our sourceforge page: http://sourceforge.net/projects/greenstone or from http://www.greenstone.org/download This is the finalised 2.81 release. It includes some bug fixes found in in 2.81rc2. If you are running a 2.81rc or 2.81rc2 please download and upgrade to this release. Our response to any mailing list questions about the 2.81rc or 2.81rc2 releases will simply be to ask you to upgrade to 2.81 first and see if that fixes the problem. As always, please report any problems or bugs to the mailing list. Many of us in the Greenstone Team will be taking leave over Christmas and throughout January. We wish all list members the best over the holiday season! An unfortunate side effect is, of course, that our responses on the mailing list may slow down over that period. We invite all list members to help each other out during this time - if you know the answer to a question someone else asks on the list, have confidence in answering, as it might be a while before one of the Greenstone team is available to reply. Happy Holidays, Oran and the rest of the Greenstone team. Release Name: 2.81 The Windows, GNU/Linux, Mac OS/X and Source distributions of Greenstone v2.81 are now available for download from our sourceforge page: http://sourceforge.net/projects/greenstone or via http://www.greenstone.org/download This is the finalised 2.81 release. It includes some bug fixes found in in 2.81rc2. If you are running a 2.81rc or 2.81rc2 please download and upgrade to this release. Important changes in this release include, in no particular order: wvWare updated -------------- We have upgraded the version of wvWare included with Greenstone in the Linux binary releases to version 1.2.4. It was not possible to do the same for the MacOS binary distribution without shipping around 80Mb of additional libraries, so the MacOS binary release still comes with version 0.7.1. MacOS users may upgrade wvWare if needed by downloading it from http://wvware.sourceforge.net/ and compiling it. Source users will also still get version 0.7.1 but may upgrade in the same way. The release notes from the 2.81rc2 release and included below: Release Name: 2.81rc2 The Windows, GNU/Linux, Mac OS/X and Source distributions of Greenstone v2.81rc2 are now available for download from our sourceforge page: http://sourceforge.net/projects/greenstone or via http://www.greenstone.org/download Important changes in this release include, in no particular order: Stability and Bug Fixes ----------------------- Some small problems in the recent 2.81rc release of Greenstone2 have been ironed out to create an overall more robust release. Some features have been restored (including realistic books and dynamic classifiers on Windows) and the LuceneWrapper.jar file has been put back into the release. GDBM ---- Greenstone now comes with it's own modified version of gdbm which can auto-detect the format of database files (ldb or bdb format) and load either format on any of Greenstone's supported platforms. This achieves a better level of portability for Greenstone collections, and allows collections built on one operating system to be served from other operating systems supported by Greenstone. Installer improvements ---------------------- * The new installer: - is now available in five languages - can now cope with being executed from a path with accented characters and other special characters. (There is still a known issue with chinese file paths, which can be avoided by simply running from c:\ or another path with no special characters.) * The source release is now provided as a platform-independent zip / tar archive * We now provide a simple binary zip / tar distribution for each platform Vista Compatibility ------------------- * When Greenstone is installed into the Program Files directory on Windows Vista, it is necessary to elevate to a higher access level to run GLI and the Greenstone server. As of this release, you can do this by launching the Start Menu items as an administrator. Just right-click the item and choose "Run as Administator", or set "Run as Adminsitrator" in the shortcut properties. Also, as a way to avoid having to elevate to higher access levels altogether, the default installation directory is now inside the current user's home folder. * Some Windows Vista users have experienced a problem when perl outputs warning messages in front of xml output passed to GLI. The error messages themselves are not fatal, but cause the xml to become invalid, resulting in a GLI crash. GLI has been modified to ignore these warning messages and thereby keep the validity of the xml. New Start Menu icons and server image ------------------------------------- Each item in a Greenstone Start Menu group is now has a unique icon so you can tell which is which at a glance. We have also added some links to the wiki and the Greenstone website for convenience. The old server image has also been replaced with the new GS2 Server logo. The release notes from the 2.81rc release and included below: Release Name: 2.81rc The Windows, GNU/Linux, Mac OS/X and Source distributions of Greenstone v2.81rc are now available for download from our sourceforge page: http://sourceforge.net/projects/greenstone or via http://www.greenstone.org/download Important changes in this release include, in no particular order: Installer: -------------- The Greenstone installer downloads are now created using only open source software, including Ant Installer (http://antinstaller.sourceforge.net/), Apache Ant (http://ant.apache.org/), our own search4j (based on launch4j http://launch4j.sourceforge.net/), and our own Greenstone release kits. We felt it was essential to move away from our existing, closed-source installer suite as it was not in the spirit of Greenstone to rely on proprietary software, and it invited the unnecessary cost of keeping the suite up-to-date. Using only open source software has also given us the freedom to customise the user experience of the installers. Where a feature was lacking in one of the open source packages, we have enjoyed the ability to "open the hood" and implement it. With the development of the Greenstone release kits we are now able to generate releases of Greenstone automatically and unattended. This process takes just 20 minutes, and it has helped us a lot in the development and testing of new features of Greenstone. We have been able to set up a feedback loop, where code committed one day is included in an automatic nightly snapshot release made available for download on our website the next day. Our users have also benefited from being able to obtain up-to-date snapshot releases of Greenstone in between our official releases. These daily snapshots are available through: http://www.greenstone.org/snapshots On Windows, the version number is included in the Start Menu which means that multiple installations of Greenstone will have their own entries in the Start Menu. The installer no longer writes to the registry, so installation no longer requires administrator privileges. ImageMagick is now bundled with Greenstone for binary web releases for all platforms (previously it was only provided on a CD-ROM release) and includes JPEG2000 support. The installer offers the option to install this or not. You can skip installing it if you already have ImageMagick previously installed. Ghostscript is now bundled with Greenstone for binary web releases for Windows and Mac. The installer offers the option to install this or not. You can skip installing it if you already have Ghostscript previously installed. Importing and Plugin Changes: ------------------------------ Plugin Restructuring: The plugins have been restructured. This has been done mostly for coding efficiency. The most noticeable change is that plugins have been renamed. xxxPlug now becomes xxxPlugin, and some have also had their names modified or expanded to be clearer. For example, DBPlug is now DatabasePlugin, PPTPlug is PowerPointPlugin. The complete list of new plugins can be seen at http://wiki.greenstone.org/wiki/index.php/Plugins. Old collections should still build okay in GLI, which will map the old plugin names to the new ones. Command line building should also work, but the configuration file won't be altered to use the new names. A lot of work has been done trying to get Greenstone to work properly with non-ascii filenames. Two versions of the filename are stored, [Source] for displaying the filename, and [SourceFile] for linking to the file from a web page. The -smart_block option (most commonly seen with HTMLPlugin) has been deprecated . Instead we have a first pass through the documents to find out which ones should be blocked. MARCPlugin and MARCXMLPlugin can now map metadata to Qualified Dublin Core as well as Dublin Core. MARCXMLPlugin now assigns metadata from metadata.xml files. EMAILPlugin now saves binary attachments as binary files on Windows ImagePlugin and PagedImagePlugin now offer the -cache_generated_images option to prevent thumbnails and screenview images being recreated each import. OAIPlugin saves the metadata as Dublin Core rather than moving it all to the ex metadata set. This means that it won't show up in the GLI unless the files are exploded. Exploding is now available for OAI records. ProCitePlugin no longer uses the pc namespace. Metadata is stored using the field names set in the workform definition, rather than using Field1Name and Field1Value etc.. -reversesort option to import.pl to be used with -sortmeta option to sort in reverse order. Tidied up OID generation. OIDtype and OIDmetadata options are now available for each plugin as well as globally from import.pl. Hashing usually occurs on the original file, but some plugins specify that hashing should be done on the Greenstone XML document. Building and Indexing Changes: ------------------------------- Improvements to Lucene incremental building. Lucene document identifiers now match Greenstone identifiers, rather than 1, 2, 3, thanks to DL Consulting. This improves search efficiency, and is another step towards true incremental building. Rebuilding with no new documents shouldn't break the index. MGPP and Lucene building tidied up. 'allfields' now means combined searching over all specified indexes (not all document metadata) for both mgpp and lucene. 'metadata' will index all metadata, but no longer reindexes metadata that has already been specified. MGPP indexing over combined fields now works properly. New collection configuration file option: infodbtype. Values include gdbm (the default), gdbm-txtgz, sqlite, mssql. This specifies what database system to use for the collection metadata database. Currently this needs to be added to collect.cfg by hand, as it is not available in GLI yet. gdbm: the default, and is what has always been used previously. This is platform dependent. It transfers between Windows and Linux, but not to/from a Mac. gdbm-txtgz: A gzipped text version of the database. At runtime, the first time this collection is accessed, it will be unpacked and converted to the appropriate GDBM database using txt2db. This is a good choice if you are creating a collection to be used on another operating system, especially if one or more of those operating systems is a Mac. sqlite: Platform independent database using SQLite. The new dynamic classifiers can be used with this database. Thanks to DL Consulting. mssql: Windows specific database using MS SQL Server. See http://wiki.greenstone.org/wiki/index.php/Using_MSSQL_for_Collection_Database for information about how to set this up. The new dynamic classifiers can be used with this database. Thanks to DL Consulting. Depositor: ------------ Collection editing using the Depositor is now enabled by default for the admin user. The metadata fields offered for each document can now easily be customised from the GLI. By default, the depositor will import and build each document into the collection when it is added. It can now be easily set up to just "deposit" the item without rebuilding. See http://wiki.greenstone.org/wiki/index.php/How_to_use_the_depositor for more information. GLI ------- A new right-click file option for binary files that go through a conversion process to be imported, such as PDF, Word and PowerPoint files. "Replace source document with HTML" will convert the original file to HTML and replace it in the collection. This means that the converted HTML (which may be unattractive) can now be modified in the collection. This is available for Remote GLI too. A new right-click file option on the collection tree background to refresh the file view. This is useful if you have manually added files to the collection outside of GLI. MetadataXMLPlugin has been moved 'below the line' in the Plugins panel so cannot be removed in GLI. If you are using GLI to add metadata, then you need this plugin. The Export As option now only exports one collection at a time. Collections can be exported as GreenstoneMETS, FedoraMETS, MARCXML and DSpace archive. 'NavigationBar pulldown' added to the list of format options - this makes the navigation 'bar' a drop down list instead of a bar across the page. Lots of work done on making the Download panel work better, including getting download processes to terminate when they are cancelled or when GLI is closed while they are still running. New panel under the Format tab, "Depositor Metadata" which allows customisation of which metadata fields should be offered in the depositor for that collection. CJK segmentation option has been added to GLI. This doesn't do proper word segmentation, but adds a space in between each CJK character. The character ranges have been expanded to work with Japanese and Korean. It is applied to metadata as well as document text. Another new feature in Greenstone v2.81 is the ability to schedule the automatic rebuilding of a greenstone collection using the GLI. There's a new panel under the Create tab allowing the scheduling of automatic collection rebuilding. Scheduling will require some configuration in order for it to work. The following link has more information on how to do this for each platform: http://wiki.greenstone.org/wiki/index.php/Scheduled_Collection_Building_from_the_Librarian_Interface Greenstone Runtime: ---------------------- New dynamic classifiers (if the collection uses sqlite or MSSQL as the collection database). These are generated at runtime so do not require the collection to be rebuilt for classifier changes. Another step towards true incremental building. See http://wiki.greenstone.org/wiki/index.php/More_about_classifiers#How_do_I_use_dynamic_classifiers.3F for more information. Thanks to DL Consulting. Large code restructuring. Code is split between common-src, build-src and runtime-src. Makes it easer to use code in other projets, such as Greenstone 3 and running Greenstone on an iPhone/iPod Touch. External links now default to going straight to the web page, rather than showing a warning page first. Improvements to the oaiserver, thanks to DL Consulting. Resumption token support has been added, and it now validates against online validation tools. Greenstone now compiles for Linux on 64-bit platforms. All programs are compiled natively for 64-bit, except for those that rely on mg/mgpp, which still need to be 32-bit compiled. As part of the configure/make process, the correct flags are automatically set, so from the developers point of view you compile up Greenstone on a 64-bit machine the exact same way you do for any other Unix-based system. Greenstone should now compile with Microsoft Visual Studio 2005, thanks to DL Consulting. FLI - Fedora Librarian Interface --------------------------------- The Fedora Librarian Interface (FLI) is very much like GLI in that it allows you to gather together your documents. It then uses Greenstone's ability to convert documents into the FedoraMETS format so that these can be ingested (put into) a Fedora repository. The process of building a collection using FLI exports documents into a repository maintained by a Fedora server rather than one maintained by Greenstone. In order to use FLI, you will need to have Fedora installed. More information on how to install Fedora and set it up to work with FLI, and how to run FLI itself, can be found in the documents: 1. Installing Fedora (2.2.1/3.0) and Fedora-related information http://wiki.greenstone.org/wiki/index.php/InstallingFedora 2. Installing Fedora Generic Search (to provide full-text indexing and searching capabilities for a Fedora repository) http://wiki.greenstone.org/wiki/index.php/InstallingFedoraGSearch 3. Running FLI, the Fedora Librarian Interface http://wiki.greenstone.org/wiki/index.php/RunningFLI Translations: -------------- Thanks to: John Rose, for help with English GLI help, French translations for GLI and Greenstone. Maxime Rouast for Greenstone French translations Celine Guimbertaud for GLI French translations Yohannes Mulugeta and Abiyot Bayou for Greenstone Amharic translations Kamal Salih for GLI Arabic translations Gerhard Riesthuis for Greenstone Dutch translations Mohan Raj Pradhan for GLI Nepali translations. Diego Spano for translating the installer's interface into Spanish. Xiaofeng Yu for translating the installer's interface into Mandarin. Doris Jung for translating the installer's interface into German. ...and many other minor improvements and bug fixes We want to ensure that Greenstone works well for you. Please report any problems to the Greenstone mailing list greenstone-users@list.scms.waikato.ac.nz. [DL Consulting (http://www.dlconsulting.com) are the world's leading suppliers of commercial consulting, customization, support, maintenance and hosting services for the Greenstone digital library software suite.] From ihw at cs.waikato.ac.nz Tue Dec 23 10:48:24 2008 From: ihw at cs.waikato.ac.nz (Ian Witten) Date: Tue Dec 23 10:48:47 2008 Subject: [greenstone-devel] Greenstone Wins Andrew W. Mellon Foundation MATC Award References: <20081214152515.B165632A79C@smtp8-g19.free.fr> Message-ID: <59E3A373-9DCF-4A84-8ACA-B93BEBABC544@cs.waikato.ac.nz> I am very pleased to announce that the University of Waikato has been awarded US$50,000 for the Greenstone project within the Third Annual Mellon Awards for Technology Collaboration (see http:// matc.mellon.org/press-release). This competition is meant "to recognize important organizational contributions to open source projects which currently or potentially provide significant benefits to at least one traditional Mellon constituency (higher education, especially the arts and humanities; libraries; museums; arts organizations; and nature conservation)." We understand that the committee was primarily impressed by Greenstone's impact in the developing world as testified by many users who supported our candidacy online, thanks to all of you who contributed recommendations. The University intends to use the award to further the Greenstone community of developers and users, particularly in developing countries. This will involve improving the documentation, making tutorial videos, and stimulating the development of Greenstone capabilities and user groups in developing countries. As part of this effort we invite proposals from the Greenstone community in developing countries for small grants (US$1000 to US $5000) which will be awarded in 2009 according to the following criteria: * one-time assistance (not a continuing subvention) for a project which will lead to sustainable follow-up: examples of activity could be organisation of user meetings or training workshops, expert missions for training and advice (particularly exchange of expertise within a given region or country), institutional exchanges or user services; * priority to regional networks and to countries and institutions in greatest need (normally grants will not available to individuals, but there could be exceptions); * priority to projects which are partially self-funded or partially funded by third parties. Detailed proposals should be addressed to John Rose , Research Associate, University of Waikato, who will correspond with the submitting parties as needed to refine their proposals. Awardees will be expected to submit a detailed evaluation report at the conclusion of their projects. cheers ian From m.mehrling at neu.edu Wed Dec 24 07:06:38 2008 From: m.mehrling at neu.edu (m.mehrling@neu.edu) Date: Wed Dec 24 07:06:48 2008 Subject: [greenstone-devel] global search and replace / global update In-Reply-To: <59E3A373-9DCF-4A84-8ACA-B93BEBABC544@cs.waikato.ac.nz> Message-ID: Hello, Does anyone have a solution for updating metadata in a batch in Greenstone? We can do search and replace in the XML, but that's not ideal. Thanks and happy holidays! Martin ************************************ Martin Mehrling Digital Systems Specialist m.mehrling@neu.edu 617.373.5885 ======================== 301 Snell Library Northeastern University Boston, Massachusetts 02115 -------------- next part -------------- An HTML attachment was scrubbed... URL: https://list.scms.waikato.ac.nz/mailman/private/greenstone-devel/attachments/20081223/e2fa6d09/attachment.html From wendy.osborn at uleth.ca Wed Dec 24 08:26:20 2008 From: wendy.osborn at uleth.ca (Wendy Osborn) Date: Wed Dec 24 08:26:32 2008 Subject: [greenstone-devel] global search and replace / global update In-Reply-To: References: Message-ID: <56750.205.200.39.132.1230060380.squirrel@webmail.uleth.ca> Hi, I know that if you load a collection into the GLI, and go to the Enrich panel, you can select multiple documents with the mouse and cntl/shift keys. Then, when you enter metadata (for example, dc.Title), this will be entered for all documents that you have selected. Hope this helps, Wendy On Tue, December 23, 2008 11:06 am, m.mehrling@neu.edu wrote: > Hello, > > Does anyone have a solution for updating metadata in a batch in > Greenstone? We can do search and replace in the XML, but that's not > ideal. > > Thanks and happy holidays! > > Martin > > ************************************ > Martin Mehrling > Digital Systems Specialist > m.mehrling@neu.edu > 617.373.5885 > ======================== > 301 Snell Library > Northeastern University > Boston, Massachusetts 02115 > _______________________________________________ > greenstone-devel mailing list > greenstone-devel@list.scms.waikato.ac.nz > https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel > -- "Masquerading as a normal person day after day is exhausting" - Anonymous Wendy Osborn Assistant Professor of Computer Science Director, Southern Alberta Digital Library Department of Mathematics and Computer Science University of Lethbridge, Alberta, Canada phone: +1 403 329 2294 email: wendy.osborn@uleth.ca www: http://www.cs.uleth.ca/~osborn