Differences

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

--- playground:playground [2009/09/26 09:14] – eoghan.ocarragain
+++ playground:playground [2014/01/21 19:29] – [4 Set up a new Solr Core - if required] chriskeene
@@ Line 1: / Line 1: @@
 ====== PlayGround ======
-====== Till Kinstler ======
-**Institution:** Service Center of the Common Library Network (GBV)
-**Role Profile:**
+Start of possible revised multi instance page.
-I am working in the digital libraries department. My main fields of action are "emerging technologies" in the digital libraries field and their application to our existing library consortium infrastructure. That includes systems analysis and design, systems integration and customization as well as coding (customization of existing code and implementation of interfaces). I deal with search technology, data interfaces (OAI-PMH, SRU, unAPI...) and some authentication stuff (Shibboleth).
+====== Installing Multiple Instances ======
+// This page refers to VuFind 2.x; for similar notes related to earlier versions, see [[..:installing_multiple_instances|this page]]. //
-**Briefly outline your experience with Vufind to date.:**
+There are a few reasons you might want to have several instances of VuFind.  Two real-life examples:
-In summer 2008 we gained a funded project (called "Suchkiste") to develop a search engine for large integrated bibliographic and fulltext data sets fed from various sources. We decided to do that with Solr instead of our legacy search
+  * You need to present the same index in slightly different ways at different URLs (i.e. filter differently or offer different themes for members of a consortium)
+  * You use VuFind as the basis for several distinct, separate systems running on the same server (i.e. a bibliography project distinct from your library catalog)
-technology. Shortly after project start we needed a prototype user frontend to
+Regardless of your use case, you probably do not need to actually install multiple copies of VuFind.  VuFind 2's flexible configuration options allow you to create multiple configurations for a single instance.
-demonstrate the power of Solr to end users and librarians. We choose VuFind as an easily customizable, open user frontend for that Solr index. Because we had some requirements not in mainline VuFind (eg. rights management, fulltext indexing), we somewhat branched/forked(?) out of the mainline development first. But finally we understood, that it is important to participate as much as possible in the mainline development (for the success of both our "Suchkiste" as well as of VuFind). That's the essence of open source projects. I think, I have a good overall overview of the VuFind architecture (including Solr and solrmarc) and some in depth knowledge of the code.
+===== 0 Decide on what kind of multi instance you need =====
+Vufind has been designed to allow much of the configuration (including theme choice) to be set per instance, while allowing those options unchanged to be inherited from the main configuration. There are a few things you will need to decide upfront when setting up a new instance:
+  * Will the new instance use the same database as other instances, or have its own? The database stores users, favorites and tags, so the question really comes down to if you want the new instance to have the same users and tags as existing instances, or to have its own. See the bottom of the page for more information
+  * Will the new instance have its own Solr Core? The Solr Core holds the searchable bibliographic records, if you want the new instance to search a separate set of records then it will need its own Solr core. See the bottom of the page for other options.
+  * Will your system use directories or hostnames to differentiate different sites?
-**Current/short-term availability:**
-VuFind is part of my day-job. Apart from some vacation in the next months, I'd say
+===== 1 Creating a New instance and local configuration directory =====
-I spend about 15 to 30 hours a week on VuFind and our VuFind based "Suchkiste" project (of course, not all time being spent on "Suchkiste" is contributing to mainline
+It is suggested (but not required) that you create a unique string for each multisite, you can use for: the directory/hostname in the url that users will request; configuration directory; etc. This helps keep things consistent and easy to manage. For example if you were setting up an instance specific for your Spingfield branch you could use 'springfield' as your string.
-VuFind directly, but there are more and more synergies). So count on me on a daily
+Run the standard install script (used during the original installation) but with the --multisite switch.
-basis. My time with VuFind isn't limited to office hours.
+<code>
+cd $VUFIND_HOME
+php install.php --multisite
+</code>
+This will prompt for the name of a new [[local settings directory]] for your instance, (e.g. using the exmaple above, 'springfield').  You will also need to specify a different base path and/or [[customizing_vufind_2.0#Modules|custom code module]] name when prompted.
-**Longer term availability**
+At the end it will prompt you to create a symbolic link for your new sites httpd-vufind.conf config file in the Apache directory. E.g.:
+<code>
+sudo ln -s /usr/local/vufind/springfield/httpd-vufind.conf /etc/apache2/conf.d/vufindspringfield
+</code>
+The location of the Apache config directory will vary on different systems.
-The first phase of our VuFind based project will be finished in Summer 2010. Until that I will be available for VuFind as described above. After that, engagement in VuFind may increase (if our project is extended beyond the scope of "Suchkiste" into a general VuFind based discovery solution for our consortium we proposed) or decrease (but not to zero, because I will have to keep "Suchkiste" running anyway).
+Note:
+  * If you have already installed a copy of VuFind in single site mode, you need to reconfigure it by re-running install.php with the --multisite switch in order to generate a multisite-capable Apache configuration. The "--multisite" switch is important, as this allows your Apache configuration to properly handle multiple sites.
+  * Windows users should be aware that running install.php creates a new "vufind.bat" file every time.  This vufind.bat file is used to set up the environment variables for other VuFind-related scripts like import-marc.bat.  If you are using custom import rules, this can affect where SolrMarc looks for your settings.  Be sure to adjust vufind.bat as needed to ensure correct importing.
+===== 2 Configure Apache =====
+==== Apache Configuration for Directory-Based Multisite ====
-| **Area of expertise/experience** | **Rating** |
+Due to the way VuFind's current default configuration uses the RewriteBase directive, having multiple VuFind configurations that all point to the same directory in their <Directory> sections prevents multisite VuFind instances from loading correctly. The following creates a symbolic link to the public directory for each instance of vufind. //(In recent versions of Windows, "mklink /D" is equivalent to the Linux "ln -s" command)//
-| Coding | 4 |
-| Interface implementation | 4 |
-| Interface planning | 1 |
-| Solr configuration | 4 |
-| ILS integration | 3 |
-| Metadata crosswalking | 4 |
-| Metadata & cataloguing issues | 3 |
-| Performance tuning & deployment | 4 |
-| Other relevant areas of experience | some experience with development tools like version control (svn, bazaaz, git) and debuggers. broad knowledge on library technology, especially (meta-)search engines |
+  - Create a symbolic link to the 'public' directory e.g. <code> ln -s $VUFIND_HOME/public $VUFIND_HOME/public-springfield </code>
+  - Edit the httpd-vufind.conf for the new instance, and change the Alias and Directory lines to point to the symbolic link created specifically for that instance. e.g. <code>
+Alias /springfield /usr/local/vufind/publicspringfield
+<Directory /usr/local/vufind/publicspringfield/>
+</code>
+Note: This is not ideal -- there should be a way to make the configuration work without duplication of the public directory.  However, until a better solution is found, this workaround will allow directory-based VuFind multisites to operate.
-**Development Skills**
+==== Apache Configuration for Host-Based Multisite ====
-PHP, Java, Javascript, Perl, SQL, XSLT, CSS, shell scripting
+If you are pointing multiple hostnames at a single server and using these to distinguish between VuFind instances, you can't simply link up the httpd-vufind.conf configurations generated by install.php.  Instead, you also need to set up virtual hosts.  Here is an example virtual host configuration for Apache, assuming hostnames of test1 and test2 and local settings directories of ms1 and ms2:
+<code>
+<VirtualHost *:80>
+    ServerName test1
+</VirtualHost>
-**How would you rate your development skills/experience?**
+Include /usr/local/vufind2/ms1/httpd-vufind.conf
-//(0 = novice; 5 = expert)//
+<VirtualHost *:80>
+    ServerName test2
+</VirtualHost>
+Include /usr/local/vufind2/ms2/httpd-vufind.conf
+</code>
+Note that when you restart Apache after adding these settings (either by editing httpd.conf or by putting a new file in Apache's conf.d directory), you will see a warning about overlapping Alias settings.  This is harmless.
-**What skills can bring to the project, other than development skills and the areas of expertise mentioned above?**
+// In some Linux distributions, it may be necessary to put the Include statements inside the <VirtualHost> blocks -- this was reported as an issue with RHEL5. //
-I organized a workshop that brought together (potential) VuFind users in Germany in June 2009. I submitted an application for a speach on VuFind at the German "Bibliothekskongress 2010" (biggest library venue in Germany) in March 2010
+===== 3 Setting up the New Instance =====
-and proposed a workshop on NGCs (including VuFind) for ELAG 2010 conference at Helsinki next June.
+The following steps should work for most setups but you may need to follow the steps that you did on initial [[installation notes|installation]].
-I am no (traditional) project management specialist, but pretty good at keeping an oversight over and working in dynamic project evolution in teams (hmmm, on "agile projects"?) and may contribute my experience there.
+  - Restart Apache for the new config to take effect.
+  - Go to <nowiki>http://my-vufind-server/my-instance-dir/Install/Home</nowiki> and fix all open issues.
+  - It may report that you need to run 'chown www-data:www-data /usr/local/vufind/springfield/config/vufind' (system usernames and file locations will of course vary) If the 'vufind' folder does not exist you will need to create it.
+  - The Web interface will not allow you to specify an existing database. If you wish to use the same database as other instances (i.e. one of the decisions listed above) you will need to specify these in the cfg file. If you wish to create a new database you can use either the web interface or the cfg file.
+  - If you are not ready to configure the ILS Driver at this time (for live holdings availabiluty) select noILS.
+===== 4 Set up a new Solr Core - if required =====
+Solr Cores hold the searchable records within vufind. Follow these steps if you want this instance to search different records to other instances of vufind on your system.
-**Briefly describe your experience on similar projects:**
+The most common setup, outlined here is an additional core on the existing Solr instance, though there are other options, see further down this page.
-As part of my job I developed the (meta-)search modules of several virtual libraries (eg. ViFa Recht, Crossasia) and some library search portals in the last years. I had to use a commercial metasearch engine toolset for that. My job was customizing it (on source code level) to specific requirements and integrating it in heterogeneous infrastructures.
+  * Shutdown vufind ($VUFIND_HOME/vufind.sh stop)
+  * Copy the existing core (usually biblio) under VuFind's solr directory to a new directory of your choice. e.g. <code>
+cd $VUFIND_HOME/solr
+cp -pr biblio springfield
+</code>
+  * If you don't want your new core to contain the records of the core you just copied from (e.g. biblio), go in to the new directory and delete (or move if you are cautious) the index folder <code>cd springfield; rm -r index</code>
+  * Edit solr/solr.xml to make the new core active. <code><core name="springfield" instanceDir="springfield"/></code>
+  * Edit conf/solrconfig.xml (in the new core directory) to adjust incorrect paths. If you have copied the biblo folder, use your text editor to search for 'biblio' and replace all occurrences (there are about two).
+  * edit $VUFIND_HOME/<instance_name>/config/vufind/config.ini, change the default_core setting under [index] to use the new core. E.g.:   default_core    = springfield
+  * If using SolrMarc (i.e. if you will be importing MARC records in to this instance), configure import/import.properties in your [[local settings directory]] to point to the new core.
+Important: When indexing, make sure that the VUFIND_LOCAL_DIR environment variable points to the correct configuration so that records are sent to the appropriate place. All cronjobs to import records in to different cores will need to set this variable.
-Before joining the library scene I did some contributions to the open source virtual learning system Moodle in its early days (around 2003).
+===== 5 Configure your new instance =====
+==== Basic Configuration ====
+If your new instance is configured almost exactly like your previous instance but with a few minor modifications, consider using the [Parent_Config] section of config.ini to inherit settings from a shared base configuration.  This will make maintenance easier over time.  The [Parent_Config] section is supported by all of VuFind's .ini files, so you can use this technique on any files that need to be customized.
+==== Custom Code ====
-**Anything else you'd like to add?**
+If you need to write code that is specific to a particular instance, or if you need to customize code in different ways for different instances, you just need to create a separate module for each instance.  This is handled for you by install.php.  See the [[customizing_vufind_2.0#Modules|custom code module]] page for more details on populating your newly created module.
+==== Custom Theme ====
-----
-====== Demian Katz ======
+VuFind's theme is determined by [[..:config.ini]] settings.  Since each instance of VuFind has its own [[..:config.ini]] in its [[local settings directory]], you can easily configure separate themes for separate instances.  Since themes can inherit from one another, it is possible to create a base theme for shared customizations and isolate minor, distinctive changes to very small, instance-specific themes.  See [[customizing the user interface]] for more details.
-**Institution:** Villanova University
+===== Further information on MySQL Databases and Solr instances =====
+==== Sharing (or not sharing) a MySQL Database ====
+If you simply create a new instance with install.php and the web-based install script, VuFind will attempt to create a separate MySQL database for each instance.  This may be desirable if each instance has its own distinct user base and tags/favorites should not flow between instances.  However, it is more common that you will want to share a database.  In this situation, just manually copy the database settings from your original instance's [[..:config.ini]] file into the new instance instead of using the "fix" link in the automatic installer.  If you use a shared base configuration as suggested [[#Basic Configuration|above]], you can even avoid duplicating credentials in multiple places.
-**Role Profile:**
+==== Using Multiple Solr Instances : Create a New Solr Instance ====
-My title is "Library Technology Development Specialist."  My primary responsibility is VuFind development, though I am also involved in other library technology projects, and I do a little bit of public service to stay involved with the broader library community.  My professional background is mixed -- I have an undergraduate degree in Computer Science and a master's degree in Library/Information Science.  I have worked in both library (a large public library) and pure-computer (web development consulting) environments in the past.
+The steps above setup a new Solr core in an existing Solr instance, which will probably be suitable for most systems. However another option is to create a New Solr Instance:
+Creating a new core usually makes more sense than creating a copy of Solr, but if your index is too large to fit on a single server, you could also copy VuFind's Solr index and startup script to another server, and reconfigure your instance to point there (using the url setting in the [Index] section of [[..:config.ini]] and, if necessary, the solr.path = REMOTE and solr.hosturl settings of SolrMarc's import.properties file).
-**Briefly outline your experience with Vufind to date.:**
+It probably does not make sense to try to run two separate instances of Solr on a single server, but if you have a good reason to do this, refer to the old [[..:installing_multiple_instances|VuFind 1.x multiple instances documentation]] for some tips; steps 4 and 6 there are still relevant.
-I first heard of VuFind when applying for my current position at Villanova.  This was my first encounter with faceted searching in a library catalog, and I was immediately impressed by the way this mixes Google-like simplicity with some of the power of the traditional structure inherent in catalogs.  In getting this job, I have inherited the original VuFind implementation.  I've only been here a few months, but I've spent the majority of my time diving into VuFind, so I'm already fairly familiar and comfortable with its code.  I can't take credit for what is already here, but I certainly look forward to helping to polish it in the future.
+===== Example shell transcript of setting up a new instance =====
+The following example creates a new instance called springfield, with a new Solr core, on server vufindserver as user libadmin.
+<code>
+libadmin@vufindserver:/etc$ cd $VUFIND_HOME
+libadmin@vufindserver:/usr/local/vufind$ php install.php --multisite
+VuFind has been found in /usr/local/vufind.
+Where would you like to store your local settings? [/usr/local/vufind/local] springfield
-**Current/short-term availability:**
+VuFind supports use of a custom module for storing local code changes.
+If you do not plan to customize the code, you can skip this step.
+If you decide to use a custom module, the name you choose will be used for
+the module's directory name and its PHP namespace.
-VuFind is the primary responsibility of my day job, so my long-term availability is not in question.  The exact amount of time I have available for VuFind coding may sometimes fluctuate as other projects come up, but I expect to be devoting at least a couple of hours (and usually more than that) to VuFind on every work day.
+What module name would you like to use? [blank for none]
+What base path should be used in VuFind's URL? [/vufind] /springfield
-**Longer term availability**
+When running multiple VuFind sites against a single installation, youneed
+to decide how to distinguish between instances.  Choose an option:
-My long-term availability is more or less the same as my short-term availability.  Villanova is very proud of its institutional role in the development of VuFind, and I don't expect its commitment to fade any time soon.
+.) Directory-based (i.e. http://server/vufind1 vs. http://server/vufind2)
+.) Host-based (i.e. http://vufind1.server vs. http://vufind2.server)
+or enter 0 to disable multisite mode.
-| **Area of expertise/experience** | **Rating** |
+Which option do you want? 1
-| Coding | 5 |
+Apache configuration written to /usr/local/vufind/springfield/httpd-vufind.conf.
-| Interface implementation | 4 |
-| Interface planning | 2 |
-| Solr configuration | 1 |
-| ILS integration | 3 |
-| Metadata crosswalking | 3 |
-| Metadata & cataloguing issues | 3 |
-| Performance tuning & deployment | 4 |
-| Other relevant areas of experience | I have four years of experience working as a single programmer doing relatively small-scale projects in a library environment.  I also have four years of experience as part of a team doing large-scale web development work in a multi-server environment.  I'm comfortable with MARC.  I've got a lot of troubleshooting experience (and a healthy degree of paranoia about security and other potential problems).  I'm fairly good at reading a book and getting up to speed on a new technology -- currently waiting for my copy of the new Solr book so I can improve my score in that area! I also normally show more modesty -- but this is a skills survey, after all! :-) |
+You now need to load this configuration into Apache.
+You can do it in either of two ways:
+    a) Add this line to your /etc/apache2/httpd.conf file:
+       Include /usr/local/vufind/springfield/httpd-vufind.conf
-**Development Skills**
+    b) Link the configuration to Apache's conf.d directory like this:
+       ln -s /usr/local/vufind/springfield/httpd-vufind.conf /etc/apache2/conf.d/vufind
-PHP, Java, Javascript, C/C++, Perl, Visual Basic, SQL, CSS
+Option b is preferable if your platform supports it,
+but option a is more certain to be supported.
+Once the configuration is linked, restart Apache.  You should now be able
+to access VuFind at http://localhost/springfield
-**How would you rate your development skills/experience?**
+For proper use of command line tools, you should also ensure that your
+VUFIND_HOME and VUFIND_LOCAL_DIR environment variables are set to
+/usr/local/vufind and /usr/local/vufind/springfield respectively.
-//(0 = novice; 5 = expert)//
+libadmin@vufindserver:/usr/local/vufind$ sudo ln -s /usr/local/vufind/springfield/httpd-vufind.conf /etc/apache2/conf.d/vufind-springfield
+[sudo] password for libadmin:
+libadmin@vufindserver:/usr/local/vufind$ ln -s $VUFIND_HOME/public $VUFIND_HOME/public-springfield
+libadmin@vufindserver:/usr/local/vufind$ vi springfield/httpd-vufind.conf
+# edited lines: Alias /springfield /usr/local/vufind/publicspringfield
+# And: Alias /springfield /usr/local/vufind/publicspringfield
+libadmin@vufindserver:/usr/local/vufind$ sudo /etc/init.d/apache2 restart
+ * Restarting web server apache2                       [ OK ]
+libadmin@vufindserver:/usr/local/vufind$ cd springfield/config/
+libadmin@vufindserver:/usr/local/vufind/springfield/config$ mkdir vufind
+libadmin@vufindserver:/usr/local/vufind/springfield/config$ sudo chown www-data:www-data /usr/local/vufind/springfield/config/vufind
+libadmin@vufindserver:/usr/local/vufind/springfield/config$ sudo chown www-data:www-data /usr/local/vufind/springfield/cache/
+libadmin@vufindserver:/usr/local/vufind/springfield/config$ # go to http://vufindserver.example.com/springfield/Install/Home
-**What skills can bring to the project, other than development skills and the areas of expertise mentioned above?**
+libadmin@vufindserver:/usr/local/vufind/springfield/config$ $VUFIND_HOME/vufind.sh stop
+Shutting down VuFind ...
-I enjoy providing troubleshooting support -- I try to respond to every question on the mailing lists that I can reasonably answer.  My work at Villanova puts me in a good position for advocacy.  I dislike unnecessary politics and don't tend to take development-related debates personally, so I can be helpful in conflict resolution (though that hardly seems necessary in the current friendly and collaborative environment I've seen on the VuFind lists!).
+STOPPED Tue Jan 21 18:45:55 GMT 2014
+libadmin@vufindserver:/usr/local/vufind/springfield/config$ cd $VUFIND_HOME/solr
+libadmin@vufindserver:/usr/local/vufind/solr$ cp -pr biblio springfield
+libadmin@vufindserver:/usr/local/vufind/solr$ cd springfield/
-**Briefly describe your experience on similar projects:**
+libadmin@vufindserver:/usr/local/vufind/solr/springfield$ rm -r index
+libadmin@vufindserver:/usr/local/vufind/solr/springfield$ cd ..
-At my first job, I wrote a simple OPAC (a clone of the III system) for use as a backup in case of emergency.  It just ingested MARC records into a simple MySQL database and displayed via PHP.  We never had need for it, so it was never put to the test, but it was a good learning experience.
+libadmin@vufindserver:/usr/local/vufind/solr$ vi solr.xml
+libadmin@vufindserver:/usr/local/vufind/solr$ # added <core name="springfield" instanceDir="springfield"/>
-I've already mentioned my previous experience with large-scale web development.
+libadmin@vufindserver:/usr/local/vufind/solr$ vi springfield/conf/solrconfig.xml
+libadmin@vufindserver:/usr/local/vufind/solr$ # replaced biblio with springfield twice
-I also have a personal project at www.gamebooks.org -- this demonstrates my ability to completely design and implement an application from scratch.  Please don't judge my CSS/HTML based on this, though -- I would do a lot differently if I had time to change it all!
+libadmin@vufindserver:/usr/local/vufind/solr$ vi $VUFIND_HOME/springfield/config/vufind/config.ini
+libadmin@vufindserver:/usr/local/vufind/solr$ # replaced biblio with springfield
+libadmin@vufindserver:/usr/local/vufind/solr$ vi $VUFIND_HOME/springfield/import/import.properties
+libadmin@vufindserver:/usr/local/vufind/springfield/import$ # replaced biblio with springfield twice
-**Anything else you'd like to add?**
+libadmin@vufindserver:/usr/local/vufind/springfield/import$ $VUFIND_HOME/vufind.sh start
+libadmin@vufindserver:/usr/local/vufind/springfield/import$ # and now to import records
-I certainly hope to get enough votes to be part of the core admin team...  but even if I don't, you can't get rid of me that easily!  I look forward to working with everyone regardless of how things turn out. :-)
+libadmin@vufindserver:/usr/local/vufind/springfield/import$ export VUFIND_LOCAL_DIR=/usr/local/vufind/springfield
+libadmin@vufindserver:/usr/local/vufind/springfield/import$ cd $VUFIND_HOME
+libadmin@vufindserver:/usr/local/vufind$ ./import-marc.sh testfile.mrc
-----
+</code>
-====== Michael Friscia ======
-**Institution:** Yale University Library
-**Role Profile:**
-Sr. Systems Programmer. I primarily work with digitized content with my main focus on developing search interfaces. I run servers and software for digital asset management, GIS, and web applications. I act as the DBA for our database applications and also handle server security. I am also in charge of our Microsoft SharePoint implementation.
-**Briefly outline your experience with Vufind to date.:**
-I was brought into Vufind last spring when I was asked to connect our CAS authentication to the system so we could activate the MyResearch components. I had a very small amount of time allowed to perform the work and spent most of it learning the web application side of the system. My involvement has grown and as we settle into new roles I expect that I will increase my participation beyond just working with the PHP files.
-**Current/short-term availability:**
-Currently I commit 10% of my time (2 days a month) to the project for programming and administrative tasks at yale. I'm willing to commit an additional 10% of my time to work in a Vufind administrative role. Vufind is part of my day job but I'm also of the type that doesn't stop writing code because a weekend or break pops up.
-**Longer term availability**
-I expect to be involved in Vufind at Yale as long as the library here is committed to using the product. I am also hiring a new programmer as the junior programmer in my department under my supervision. This new programmer will also be applying 10% of their time to the product.
-| **Area of expertise/experience** | **Rating** |
-| Coding | 5 |
-| Interface implementation | 5 |
-| Interface planning | 3 |
-| Solr configuration | 1 |
-| ILS integration | 1 |
-| Metadata crosswalking | 1 |
-| Metadata & cataloguing issues | 3 |
-| Performance tuning & deployment | 4 |
-| Other relevant areas of experience | SQL Security and general SQL/URL injection attack prevention and monitoring. |
-**Development Skills**
-PHP, Java, Javascript, C/C++, C#, Perl, Visual Basic, SQL, XSLT, CSS, PL/SQL
-**How would you rate your development skills/experience?**
-//(0 = novice; 5 = expert)//
-**What skills can bring to the project, other than development skills and the areas of expertise mentioned above?**
-I've done a lot with project management and also have experience with microsoft project and similar open office flavor. I have experience in hosting events, training sessions and have presented on numerous occassions in venues such as NERCOMP.
-**Briefly describe your experience on similar projects:**
-I worked on Connecticut College's student electronic portfolio project. During this time I spent a lot of time working with the open source portfolio initiative. We did not use the product at Connecticut College but I stayed on the project as a developer and worked out a lot of the integration problems between SCT Banner/PeopleSoft and third party products.
-**Anything else you'd like to add?**
-The Yale University Library has a large number of staff committeed to this project. For me, it was an easy sell. Once an opportunity came up, I was quick to jump onboard to begin participating in the development.
-My primary development environment is .Net but I've been a PHP programmer since 1998. I worked primary on unix systems from 1985 to 1999 when I switched over to Windows/ColdFusion/.Net. The onyl reason I gave my performance tuning skills a 4 and not a 5 is that I have not done much on unix systems at all in a number of years. But on my desk I run a Fedora 10 machine, windows xp and an iMac. I consider myself to be "platform neutral" and don't bother with the anti mac, anti java, anti .net arguments and all the other politics in computing. I just like to write code and don't care what system it is on.
-----
-====== Andrew Nagy ======
-**Institution:** Serials Solutions
-**Role Profile:**
-Software Engineer, Market Expert, Product Manager.
-**Briefly outline your experience with Vufind to date.:**
-Founder and Lead Developer
-**Current/short-term availability:**
-% of my day job.  Plus random nights and weekends.
-**Longer term availability**
-Full commitment.
-| **Area of expertise/experience** | **Rating** |
-| Coding | 5 |
-| Interface implementation | 5 |
-| Interface planning | 3 |
-| Solr configuration | 5 |
-| ILS integration | 5 |
-| Metadata crosswalking | 5 |
-| Metadata & cataloguing issues | 4 |
-| Performance tuning & deployment | 3 |
-| Other relevant areas of experience |   |
-**Development Skills**
-PHP, Java, Javascript, SQL, XSLT, CSS
-**How would you rate your development skills/experience?**
-//(0 = novice; 5 = expert)//
-**What skills can bring to the project, other than development skills and the areas of expertise mentioned above?**
-Administration, Outreach, Marketing, Event Organization
-**Briefly describe your experience on similar projects:**
-PEAR::Structures_DataGrid
-SolrMarc
-**Anything else you'd like to add?**
-----
-====== Mark Sandford ======
-**Institution:** William Paterson University
-**Role Profile:**
-Special Formats Cataloger (Librarian)
-**Briefly outline your experience with Vufind to date.:**
-First installation was about a year ago.  We recently started testing VUFind in-house for usability as a replacement for Voyager OPAC.  I am in charge of the installation, customization, etc.
-**Current/short-term availability:**
-**Longer term availability**
-The library is committed to implementing VUFind as soon as it is feasible.  This is a slow process because I am solely responsible for it right now, though that will change as we near production.  I can dedicated several hours per week to VUFind as a part of my job.
-| **Area of expertise/experience** | **Rating** |
-| Coding | 2 |
-| Interface implementation | 4 |
-| Interface planning | 1 |
-| Solr configuration | 2 |
-| ILS integration | 3 |
-| Metadata crosswalking | 1 |
-| Metadata & cataloguing issues | 5 |
-| Performance tuning & deployment | 1 |
-| Other relevant areas of experience |   |
-**Development Skills**
-PHP, CSS
-**How would you rate your development skills/experience?**
-//(0 = novice; 5 = expert)//
-**What skills can bring to the project, other than development skills and the areas of expertise mentioned above?**
-I am primarily a cataloger, though I perform a lot of duties that would normally fall to a Systems Librarian.  I have a very good understanding of how Voyager's database structure works and how that connects to the MARC record.
-**Briefly describe your experience on similar projects:**
-None
-**Anything else you'd like to add?**
-I would view my work in the admin group as primarily being a voice for catalogers (and uers) and to lend my expertise to the group in that respect.  However, I can handle basic coding well enough to understand the developer side of the conversation as well.
-----
-====== Clay Hill ======
-**Institution:** Mississippi State University
-**Role Profile:**
-I manage a team of web developers. I am also a developer myself.
-**Briefly outline your experience with Vufind to date.:**
-I have installed it and tweaked it to work with sip2 and sirsi unicorn.
-**Current/short-term availability:**
-I think I'll be able to contribute a few hours a week. hopefully more. This is a part of my day-job.
-**Longer term availability**
-Once we get this thing working to our likeing. We will be committed to vufind. I am working on Vufind daily. I see Vufind being with Msstate for a long time.
-| **Area of expertise/experience** | **Rating** |
-| Coding | 4 |
-| Interface implementation | 5 |
-| Interface planning | 4 |
-| Solr configuration | 2 |
-| ILS integration | 3 |
-| Metadata crosswalking | 2 |
-| Metadata & cataloguing issues | 3 |
-| Performance tuning & deployment | 3 |
-| Other relevant areas of experience | I know a fair amount about a bunch of stuff. Expert at none. :) |
-**Development Skills**
-PHP, Java, Javascript, C/C++, C#, Perl, Ruby, Visual Basic, Python, SQL, XSLT, CSS, classic asp and .net :)
-**How would you rate your development skills/experience?**
-//(0 = novice; 5 = expert)//
-**What skills can bring to the project, other than development skills and the areas of expertise mentioned above?**
-I am a project manager, a heck of a publicist. I can make a great alfredo sauce.
-**Briefly describe your experience on similar projects:**
-I have beta tested software since the early 90's.
-**Anything else you'd like to add?**
-I have a candid attitude, I hope that's not misinterpreted. I am commited to Vufind. I have been using it for a short 2 months. I am extremely impressed and I am eager to get up to speed and help out.
-----
-Use this space to mess with the wiki syntax
 ---- struct data ----
 ----