Greenstone Wiki

User Tools

Site Tools

You are here: index » en » user » gs2_or_gs3
en:user:gs2_or_gs3

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:user:gs2_or_gs3 [2018/07/29 23:28] – [Disadvantages of Greenstone3] kjdonen:user:gs2_or_gs3 [2023/03/13 01:46] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +
 +
 +
 ======Greenstone2 or Greenstone3====== ======Greenstone2 or Greenstone3======
 Greenstone3 is a complete redesign and reimplementation of the original Greenstone3 is a complete redesign and reimplementation of the original
Line 25: Line 28:
 across different servers as necessary. This modular design increases the flexibility  across different servers as necessary. This modular design increases the flexibility 
 and extensibility of Greenstone. Advantages of Greenstone3 include: and extensibility of Greenstone. Advantages of Greenstone3 include:
-  * **Distributed Computing Support**  It is easy for different Greenstone3 installations to communicate with each other and serve each others collections. SOAP connections allow the library to run in a distributed fashion.   
-  * **Web Service**  Greenstone3 allows collections to be served in [[http://en.wikipedia.org/wiki/XML|XML]] format over [[http://en.wikipedia.org/wiki/SOAP|SOAP]], which makes the information in Greenstone collections not only human-readable but also machine-readable.  
   * **Themes** Greenstone3's default interface is built around JQuery themes, allowing you to completely change the color scheme of your library in seconds.   * **Themes** Greenstone3's default interface is built around JQuery themes, allowing you to completely change the color scheme of your library in seconds.
   * **Interface Customization**  Greenstone3 replaces macros with XML and XSLT for customising the visual appearance of your collections. This affords users more power over the look-and-feel of collections. The library program generates page data in XML, which is converted to HTML using XSLT. All formatting is done using XSLT, so it makes it easier to customize than Greenstone2 in which some of the HTML is output by the library, and some by the macro files. It is very easy to get back the data in XML, if you want to use it for other purposes.    * **Interface Customization**  Greenstone3 replaces macros with XML and XSLT for customising the visual appearance of your collections. This affords users more power over the look-and-feel of collections. The library program generates page data in XML, which is converted to HTML using XSLT. All formatting is done using XSLT, so it makes it easier to customize than Greenstone2 in which some of the HTML is output by the library, and some by the macro files. It is very easy to get back the data in XML, if you want to use it for other purposes. 
Line 34: Line 35:
   * **Multiple sets of collections and multiple interfaces**  A single Greenstone3 installation can have multiple sets of collections and multiple interface definitions. Greenstone2, on the other hand, has a single collect directory, and a single set of macros. Greenstone3 has multiple "sites" each of which has its own collect directory, and multiple "interfaces" each of which has its own set of XSLT files. Any site can be served using any interface.    * **Multiple sets of collections and multiple interfaces**  A single Greenstone3 installation can have multiple sets of collections and multiple interface definitions. Greenstone2, on the other hand, has a single collect directory, and a single set of macros. Greenstone3 has multiple "sites" each of which has its own collect directory, and multiple "interfaces" each of which has its own set of XSLT files. Any site can be served using any interface. 
   * **Addition of New Features**  The library runtime is written in Java and is modular, making it a lot easier to add new features should they be needed.    * **Addition of New Features**  The library runtime is written in Java and is modular, making it a lot easier to add new features should they be needed. 
 +  * **Distributed Computing Support**  It is easy for different Greenstone3 installations to communicate with each other and serve each others collections. SOAP connections allow the library to run in a distributed fashion.  
 +  * **Web Service**  Greenstone3 allows collections to be served in [[http://en.wikipedia.org/wiki/XML|XML]] format over [[http://en.wikipedia.org/wiki/SOAP|SOAP]], which makes the information in Greenstone collections not only human-readable but also machine-readable. 
  
 =====Disadvantages of Greenstone3===== =====Disadvantages of Greenstone3=====
en/user/gs2_or_gs3.1532906909.txt.gz · Last modified: 2018/07/29 23:28 by kjdon