Wiki - Release Notes

Release Summary

The Gender Initiative data system includes three subsystems: Calendar of events, Contacts, and Library resource records. The underlying data for these systems is stored in an Access database. The systems are accessed by users through a collection of web pages that can be posted on any ASP-enabled server.

The calendar displays current events according to month, and holds information pertaining to the dates, times, location, event sponsor, etc., for each event. In this release, users can view, add, edit, and delete event information, and internal Gender Initiative members can review requested changes to the calendar by the general public.

The contacts system stores information pertaining to a person or organization with whom the Gender Initiative has come into contact, including name, address, phone numbers, programs, lectures, and general comments. In this release, users can view contact information, and internal Gender Initiative users can add, edit, and delete contact records.

The library system stores information pertaining to resources found in the Gender Initiative's private library, including article title, author, and publication information. In this release, users can view resource information, and internal Gender Initiative users can add, edit, and delete resource records.

This release includes a search page as a way for users to access calendar, contact, and library records.

This release includes a login page for Gender Initiative members to access internal functions, and makes a distinction between the information and options available to internal versus public users of the system at all times.

A more specific description of this release's functionality and limitations follows.

Requirements Implemented

For a more detailed explanation of each of these requirements, see the Software Requirements Specification.

2.2	Calendar Of Events	PARTIALLY
2.2.1	Calendar User Interface	PARTIALLY
2.2.2	Public User Functions	PARTIALLY
2.2.2.1	View	YES
2.2.2.1.1	View Event	YES
2.2.2.1.1.1	Viewable fields	YES
2.2.2.1.2	View Calendar	YES
2.2.2.2	Submit	PARTIALLY
2.2.2.2.1	Submit event	YES
2.2.2.2.1.1	Required fields	YES
2.2.2.2.1.2	Optional fields	YES
2.2.2.2.2	Submit event edit request	YES
2.2.2.2.3	Submit event removal request	YES
2.2.2.2.4	Submit event repeat request	NO
2.2.2.2.4.1	Event repeat required fields	NO
2.2.2.2.4.2	Event repeat optional fields	NO
2.2.3	Internal User Functions	YES
2.2.3.1	Review event submissions	YES
2.2.3.1.1	View event submissions	YES
2.2.3.1.2	Notification of event submission	YES
2.2.3.1.2.1	Users to be notified	YES
2.2.3.1.2.2	Link to event submissions	YES
2.2.3.1.3	Approve event submission	YES
2.2.3.1.4	Reject event submission	YES
2.2.3.2a	View event	YES
2.2.3.2	Add event	YES
2.2.3.2.1	Required fields	YES
2.2.3.2.2	Optional fields	YES
2.2.3.3	Edit event	YES
2.2.3.4	Delete event	YES
2.3	Contacts	PARTIALLY
2.3.1	Contacts User Interface	PARTIALLY
2.3.2	Public User Functions	PARTIALLY
2.3.2.1a	View contact	YES
2.3.2.1a.1	Viewable fields	YES
2.3.2.1	View event contact	NO
2.3.2.2	Search events from contact	NO
2.3.2.3	Search contacts	PARTIALLY
2.3.2.3.1	Search contacts by query	PARTIALLY
2.3.2.3.1.1	Query fields	PARTIALLY
2.3.2.4	Add contact to event	NO
2.3.2.4.1	Search contacts	NO
2.3.2.4.2	Add search result	NO
2.3.3	Internal User Functions	PARTIALLY
2.3.3.1	Add contact	YES
2.3.3.1.1	Required fields	YES
2.3.3.1.2	Optional fields	YES
2.3.3.2	View contact	YES
2.3.3.3	Search contacts	NO
2.3.3.3.1	Search contact from event	NO
2.3.3.3.1.1	Add contact from event	NO
2.3.3.4	Edit contact	YES
2.3.3.6	Delete contact	YES
2.4	Library Resource Catalog	PARTIALLY
2.4.1	Library User Interface	PARTIALLY
2.4.2	Public User Functions	PARTIALLY
2.4.2.1	View contact from resource	NO
2.4.2.2	Subject search	YES
2.4.2.3	Search resources from contact	NO
2.4.3	Internal User Functions	PARTIALLY
2.4.3.1	Add resource	YES
2.4.3.1.1	Required fields	YES
2.4.3.1.2	Optional fields	YES
2.4.3.2	Edit resource	YES
2.4.3.3	Delete resource	YES
2.4.3.4	Manage subject headings	NO
2.4.3.4.1	Control available subject headings	NO
2.4.3.4.2	Choose record subject headings	NO

Known Issues

Viewing an event edit request which edits an event that has been deleted will not reflect that any changes have been made nor that original has been deleted.
Events that end at midnight may not display correctly on the calendar view.
Because the browser caches pages, after logging out you may get a page showing you logged in. To fix this, hit Reload.
Contact first name / last name and organization are shown as required fields, even though only one or the other is required. Same for submitter phone/email.
On loading an edit page, phone numbers will be transferred correctly only if they are 10, 7, or 4 digits long. No provision is made for phone numbers (such as international) longer than 10 digits.
No maxlength property for textareas: Fields that appear as textarea in UI will not keep the user from entering more characters than the database will store in that field - though most text areas are stored as type Memo in the database and as such have no length limitations.
"Highlighting" modified fields (currently in red) for an event edit request requires appending the special keyword "HIGHLIGHT" to the field value, which is then interpreted and removed by the writeOutputField or writeOutputPhoneField function. It would be nice if this could be thought through and redone in a more flexible way.
Search page only returns results for a single search term or phrase found together in the same field for a record. Dates for calendar events also have to be entered in exactly the right way (MM/DD/YYYY with zeros preceeding single-digit months or dates omitted) for the search page to find them.
On the "Add Resource" page, a date is entered by default as Jan1 if no other date is entered. This should be modified so a date does not appear if there is no selected date.
There is no way to enter line breaks in the Contacts memo fields (comments).
Netscape 4.7 has trouble displaying some of the pages correctly. In addition, the HTML is not valid HTML.