User Interface Requirements

1. View System Status: The user will be able to see the current system status including the following:
   1. The zebrasrv status: The user will see if zebrasrv is running or not.
   2. The name of the last source to be harvested.
   3. The time and date of the last successful harvest.
2. View System properties: The user will be able to see the system properties and property values stored in the h2qConfig.properties file.
3. View H2Q Help: The user will be able to view help for each of the user actions.
4. Add OAI Source: The user will be able to add an OAI Source for harvesting and indexing.
   1. Fields: The user will be able to enter the following:
      1. URL (required): The user will enter a url, select it from a list, or select a collection name that encapsulates a url.
      2. Set name (optional): The user can enter a set name, select if from a list, or select a collection name that encapsulates the set name.
      3. Output File Name(required): The user will enter an output file name to be used as the database name and name of folder containing the harvested xml files.
      4. How often(default: 1 day): The user can enter a value for frequency of harvesting. Valid numbers are integers greater than zero. Valid units are minutes, hours, days.
      5. Harvesting Enabled(default: yes): The user can specify if harvesting is enabled for the OAI source. A "yes" value means that the source will be harvested immediately after the user clicks "OK" and subsequently harvested according to the "How Often" (4.1.4) value. A "no" value means that the source will not be harvested until the user edits the source and changes the value to "yes".
   2. Actions: The user will be able to execute the following actions:
      1. OK: The system will validate the user input, create a new source object, schedule harvesting for that source, and index the zebra database after a successful harvest.
      2. Cancel: The system will confirm that the user wants to cancel the "Add OAI Source" task. If the user confirms, the system will close the task without saving or harvesting. If the user does not confirm, the system will return the user to the "Add OAI Source" task.
5. Edit OAI Source: The user will be able to edit an existing OAI Source for harvesting and indexing.
   1. Editable Fields: The user will be able to edit the following:
      1. URL: The user may edit a url, select it from a list, or select a collection name that encapsulates a url. If the user changes the URL, the system will prompt the user to confirm that changing the URL will result in a full-harvest and the previous harvests from the previous URL will be deleted.
      2. Set name: The user may edit a set name, select if from a list, or select a collection name that encapsulates the set name. If the user changes the set name, the system will prompt the user to confirm that changing the set name will result in a full-harvest and the previous harvests from the previous set name will be deleted.
      3. How often: The user may edit the value for frequency of harvesting. Valid numbers are integers greater than zero. Valid units are minutes, hours, days.
      4. Harvesting Enabled(default: yes): The user can specify if harvesting is enabled for the OAI source. A "yes" value means that the source will be harvested immediately after the user clicks "OK" and subsequently harvested according to the "How Often" (5.1.3) value. A "no" value means that the source will not be harvested until the user edits the source and changes the value to "yes".
   2. Read-only fields
      1. Output File Name: The user will see the output file name that is used as the database name and name of folder containing the harvested xml files.
      2. First Created: The user will see the time and date that the source was first created in the H2Q system.
      3. Last Harvested: The user will see the time and date that the source was last successfully harvested.
   3. Actions: The user will be able to execute the following actions:
      1. OK: The system will validate the user input, edit the current source object, re-schedule harvesting for that source (for that source), and index the zebra database after a successful harvest.
      2. Cancel: The system will confirm that the user wants to cancel the "Add OAI Source" task. If the user confirms, the system will close the task without saving or harvesting. If the user does not confirm, the system will return the user to the "Edit OAI Source" task.
6. List Sources: The user will view a list of OAI sources
   1. View Information: The user will see the following for each source:
      1. Status: The system will report harvesting and indexing status for each source. The system will track the number of times a harvest has failed for a particular source and reset the number upon a successful harvest.
      2. File Name: The user will see the given File Name for the OAI Source that will correspond with the database name and the folder name storing the harvested xml files.
      3. URL: The user will see the url for the given OAI source.
      4. Set: The user will see the set name for the given OAI source.
      5. Collection Name(optional): The user may see a collection name for the given OAI source.
      6. Last Updated: The user will see the date of the last user update to the given OAI source.
   2. Actions: For each source in the list, the user will be able to perform the following actions:
      1. Edit: The user can edit an OAI Source. See #2 Edit Source.
      2. Remove: The user can remove an OAI Source. The Source will be removed from the list and the system will delete the corresponding database tables and xml files.
7. Integration with Ockham: The system will harvest Ockham and present the resulting OAI Collections to the user. The user may select a Collection or a URL & Set Name as a source to be harvested.

• Future UI Requirements