Differences

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

--- playground:playground [2009/09/26 09:15] – eoghan.ocarragain
+++ playground:playground [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-====== PlayGround ======
-====== 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.
-----
----- struct data ----
-----