Since the new version of Greenstone now includes the remote GLI client, we are keen to test out a server install and to use the client to connect to a portable server, either linux or osx based.
First we download the .dmg from http://www.greenstone.org and extract and run the 2.82 installer. This installs to /Users/gnickers/Greenstone and we select the core, imagemagick and ghostscript. We also enable the Admin pages checkbox with the usual password.
Click Install and away it goes, completing in 42 seconds. In the Greenstone folder we find a bunch of directories:
apache-httpd - the web server
gli - the librarian interface for building collections
bin - executables
collect - collections
image - CSS files and images
The greenstone server interface (GSI) is an application to start/stop the local library server. On Linux and OSX it uses the apache web server that comes with Greenstone.
I see the gs2-server.sh file is there and on linux this requires a trip to the terminal and the ./gs2-server.sh command but it's been years since i did much in the cli in osx. We try it out in terminal and it works. However, port 80 is in use or can't be assigned. (apache already running?) so it assigned port 8282 and pops up a dialog box. We click Enter Library and the server control panel starts up in the web browser. However Safari returns 'can't connect to server'.
Curious to see if localhost is running we try port 80 but nothing. So what's using port 80? We don't have skype installed...
Ubuntu Install
So we try the linux version. The installer program runs just the same. We open a shell and cd Greenstone and type:
./gs2-server.sh
and get the same message about 'port 80 in use or can't be assigned'. We click Enter Library but get the same 'Failed to Connect to locahost:8282
Time for some research....
Monday, September 28, 2009
Wednesday, September 23, 2009
HeidiSQL tool for mySQL
We have been using XAMPP on USB sticks for teaching for some time now. One of the problems has been the limited tools to manage the mySQL database server:
- phpmyadmin web interface
- mysql command line text-mode client
While the command line client is fast and has a lot of advantages it is somewhat an alien way of working for students. The web interface is more familiar but is slow and very old web like.
Of course you can use some of the great third-party tools for mySQL if they are installed but the general use labs only have the mySQL query browser. My favorite 2rd party tool is Navicat for OSX, I first purchased it years ago for a database project, it did everything well. But it is commercial (although they now have a free Lite version) so out of the student's reach. What we really wanted was a nice GUI tool that would run as a portable application.
Well, amazing enough such a creature exists and it is called HeidiSQL. Goto http://www.heidisql.com/ and have a look. There is a portable version that takes only 4.6 mb of space on a USB Stick.
Run the .exe installer and point it to the PortableApps folder on your USB stick. You don't have to install it there but if you do then it automatically gets added to the Portable Apps menu. Note that you don't actually have to have Portable Apps installed to run any portable application, you can just run the .exe file. However, having a nice menu system is a bonus that helps keep things organized.
When you run the program it brings up a connection manager for your session. Just fill in localhost for the IP, root for the User and click Connect! If you do not specify a database it will show you all the databases on the mySQL server, if you specify a database it only shows you that one.
For a light client it has lots of features, import/export of data and sql files, data search/edit etc, user account admin, SQL queries, database admin and it can even create views. What's not to like?
I think we have found a winner for class use. For more information goto:
http://code.google.com/p/heidisql/ which provide the following list of features:
- phpmyadmin web interface
- mysql command line text-mode client
While the command line client is fast and has a lot of advantages it is somewhat an alien way of working for students. The web interface is more familiar but is slow and very old web like.
Of course you can use some of the great third-party tools for mySQL if they are installed but the general use labs only have the mySQL query browser. My favorite 2rd party tool is Navicat for OSX, I first purchased it years ago for a database project, it did everything well. But it is commercial (although they now have a free Lite version) so out of the student's reach. What we really wanted was a nice GUI tool that would run as a portable application.
Well, amazing enough such a creature exists and it is called HeidiSQL. Goto http://www.heidisql.com/ and have a look. There is a portable version that takes only 4.6 mb of space on a USB Stick.
Run the .exe installer and point it to the PortableApps folder on your USB stick. You don't have to install it there but if you do then it automatically gets added to the Portable Apps menu. Note that you don't actually have to have Portable Apps installed to run any portable application, you can just run the .exe file. However, having a nice menu system is a bonus that helps keep things organized.
When you run the program it brings up a connection manager for your session. Just fill in localhost for the IP, root for the User and click Connect! If you do not specify a database it will show you all the databases on the mySQL server, if you specify a database it only shows you that one.
For a light client it has lots of features, import/export of data and sql files, data search/edit etc, user account admin, SQL queries, database admin and it can even create views. What's not to like?
I think we have found a winner for class use. For more information goto:
http://code.google.com/p/heidisql/ which provide the following list of features:
With HeidiSQL you will be able to
- generate nice SQL-exports
- synchronize tables between two databases
- manage user-privileges
- import text-files
- export table-data as CSV, HTML, XML and SQL
- browse and edit table-data using a comfortable grid
- create and edit stored procedures
- batch-insert ascii or binary files into tables
- write queries with customizable syntax-highlighting and code-completion
- monitor and kill client-processes
- connect to servers via commandline
- and much more
MARC Records into Greenstone
This was a test of getting MARC record imported in Greenstone digital library software and automatically filling in the Dublin Core metadata elements
The first step was to get the MARC records into a file. There are three ways to do this:
- save some records from a library OPAC
- find a file of marc records on the Internet
- use a Z39.50 client
We tested the first two methods. The library OPAC was straightforward, you do a search and tag or select the records you want and then view them. There are several options such as ProCite and MARC format, so we selected MARC and the local disk option and saved them to a file.
The downloaded file was called export.txt so we renamed it export.marc for importing into Greenstone.
Importing
1. We ran the GLI for greenstone and created a new collection
2. Click the Gather tab, expand the Local Filespace
3. Drag export.marc into the Collection window and ADD the MARCplugin
4. Right-click on export.marc in the Collection window and select Explode Metadata Database
5. Select Dublin Core from the metadata_set pulldown and click Explode
6. Click the Design tab
7. Select Marcplugin and click Remove Plugin
You can now build and preview the collection but the display will be all wrong. Remove the default search and browsing indexes. Now you have to create indexes based on the Dublin Core metadata set, for example an Author index:
1. Click Design, Browsing Classifiers
2. Select AZcompactlist from the Select Classifier pulldown menu
3. Click Add Classifier
4. Select dc.Creator from the metadata pulldown menu
5. Place a tickmark in the allvalues checkbox
6. Place a tickmark in the buttonmane checkbox and type in Authors as a menu label
Let's also add a Subject index:
1. Select AZcompactlist from the Select Classifier pulldown
2. Click Add Classifier
3. Select dc.Subject from the metadata pulldown
4. Tick the allvalues checkbox
5. Click OK
Build and preview to see the new indexes, but the display will still be a bit off. The next step is to change the formatting instructions for the web pages:
1. Click Format, Format Features
2. Delete the first and last lines in the HTML Format String box
Once the above two lines are deleted you can refresh the web pages - html or css changes do not require a rebuild. However, if you click on the icon to view the document no text is displayed and the document heading is wrong.
1. Click on Format, Format Features
2. Select DocumentHeading in the Choose Feature pulldown
3. Delete the text in the HTML Format String box
This gets red of the incorrect document header. Now to fix the 'no text' document:
1. Click Format, Format Features
2. Select DocumentText in the Choose Feature pulldown
3. Replace [text] with the following HTML code:
You can add a little inline CSS to pretty up the presentation but you get the idea. The final step is to remove the buttons as there is nothing to detach and highlighting makes no sense in a short bibliographic record:
1. Click Format, Format Features
2. Select Document Buttons
3. Delete the text in the HTML Format String box
You can now preview the collection. Obviously there is a lot more that could be done such as having the index nodes indicate how many records they contain using the [numleafdocs] variable and we could make a much nicer display by tweaking the external style sheet....
Appendix
I downloaded the Terry Reese's excellent MARCedit program to do a little experiment on the marc records files i have saved from the library OPAC. I wanted to test out converting MARC to Dublin Core. Here's what i did:
1. Renamed the export.marc file to export.mrc (marcdedit does not recognize .marc extension)
2. Ran MARCedit and selected MARCbreaker
3. Select MARC -> Dublin Core
4. Choose export.mrc as the input file
4. Choose an export file of weldon_dc.txt and clicked Execute
It created a plain text XML file that uses rdf:description and replaces all the MARC tags with Dublin Core tags. Here is a snippet of the file of records:
Accelerated SQL Server 2008 [electronic resource] /
Walters, Robert E.
Coles, Michael.
Farmer, Donald.
Ferracchiati, Fabio.
Rae, Robert.
SpringerLink (Online service)
text
Berkeley, CA : Robert Walters,
2008.
eng
Data structures (Computer science)
Springer eBooks.
http://dx.doi.org/10.1007/978-1-4302-0606-4
The problem is that i cannot get this file to explode in Greenstone, it imports as one file of one record using LOMplug. I'll have to do some research on this tomorrow...
The first step was to get the MARC records into a file. There are three ways to do this:
- save some records from a library OPAC
- find a file of marc records on the Internet
- use a Z39.50 client
We tested the first two methods. The library OPAC was straightforward, you do a search and tag or select the records you want and then view them. There are several options such as ProCite and MARC format, so we selected MARC and the local disk option and saved them to a file.
The downloaded file was called export.txt so we renamed it export.marc for importing into Greenstone.
Importing
1. We ran the GLI for greenstone and created a new collection
2. Click the Gather tab, expand the Local Filespace
3. Drag export.marc into the Collection window and ADD the MARCplugin
4. Right-click on export.marc in the Collection window and select Explode Metadata Database
5. Select Dublin Core from the metadata_set pulldown and click Explode
6. Click the Design tab
7. Select Marcplugin and click Remove Plugin
You can now build and preview the collection but the display will be all wrong. Remove the default search and browsing indexes. Now you have to create indexes based on the Dublin Core metadata set, for example an Author index:
1. Click Design, Browsing Classifiers
2. Select AZcompactlist from the Select Classifier pulldown menu
3. Click Add Classifier
4. Select dc.Creator from the metadata pulldown menu
5. Place a tickmark in the allvalues checkbox
6. Place a tickmark in the buttonmane checkbox and type in Authors as a menu label
Let's also add a Subject index:
1. Select AZcompactlist from the Select Classifier pulldown
2. Click Add Classifier
3. Select dc.Subject from the metadata pulldown
4. Tick the allvalues checkbox
5. Click OK
Build and preview to see the new indexes, but the display will still be a bit off. The next step is to change the formatting instructions for the web pages:
1. Click Format, Format Features
2. Delete the first and last lines in the HTML Format String box
Once the above two lines are deleted you can refresh the web pages - html or css changes do not require a rebuild. However, if you click on the icon to view the document no text is displayed and the document heading is wrong.
1. Click on Format, Format Features
2. Select DocumentHeading in the Choose Feature pulldown
3. Delete the text in the HTML Format String box
This gets red of the incorrect document header. Now to fix the 'no text' document:
1. Click Format, Format Features
2. Select DocumentText in the Choose Feature pulldown
3. Replace [text] with the following HTML code:
You can add a little inline CSS to pretty up the presentation but you get the idea. The final step is to remove the buttons as there is nothing to detach and highlighting makes no sense in a short bibliographic record:
1. Click Format, Format Features
2. Select Document Buttons
3. Delete the text in the HTML Format String box
You can now preview the collection. Obviously there is a lot more that could be done such as having the index nodes indicate how many records they contain using the [numleafdocs] variable and we could make a much nicer display by tweaking the external style sheet....
Appendix
I downloaded the Terry Reese's excellent MARCedit program to do a little experiment on the marc records files i have saved from the library OPAC. I wanted to test out converting MARC to Dublin Core. Here's what i did:
1. Renamed the export.marc file to export.mrc (marcdedit does not recognize .marc extension)
2. Ran MARCedit and selected MARCbreaker
3. Select MARC -> Dublin Core
4. Choose export.mrc as the input file
4. Choose an export file of weldon_dc.txt and clicked Execute
It created a plain text XML file that uses rdf:description and replaces all the MARC tags with Dublin Core tags. Here is a snippet of the file of records:
The problem is that i cannot get this file to explode in Greenstone, it imports as one file of one record using LOMplug. I'll have to do some research on this tomorrow...
Subscribe to:
Posts (Atom)