RM README v0.06 (RDM 1.23, 14/03/03) Renamed source files more consistently; fixed compatability problem with jdom beta 8 (bug 1); allow search queries containing both "/@" and "@" in paths; threaded remote search; set up diagnostic handler to use XML file for list of diagnostics; fixed problem with availability determination; added openURL client/server modules (latter not fully working); checked compatibility with current JDOM/xalan releases; initial DTDs for queries and responses v0.05 (23/07/02) Improved XQuery parsing (queries now recursively dismantled; adding handling of AND/OR queries) (note that this involves slight changes to interface); get list of available resources request; get list of resource types request v0.041 (24/06/02) Fix bug so that adminstrative data correctly created when there is no data in database entry for resource. (Not a full release.) v0.04 (22/06/02) Allow retrieval of single resource by resource_id, search resources by create/modify date, fix bug to return administrative data with resource listing in search response. v0.03 (18/06/02) Searching/sorting by any resource text field, searching by keyword, limiting maximum number of search results returned, starting return at specified result, resource editing functionality (create/edit/delete resource), permitting requests according to IP address of service, multiple line requests understood; re-organised files to create uk.ac.angel/uk.ac.angel.rm packages v0.02 (21/05/02) Optional filtering by group list/IP address to show resources available to current user v0.01 (15/05/02) First release, allows retrieval of subject listing, searching by subject ID & term, initial letter of resource name and string in name, results sorted by name KNOWN BUGS Format: Bug number (reporter, date; affected versions) - description 3 (JP, 24/09/02; v0.05) - subjects which are not being used are expected to disappear from the database; this doesn't seem to happen. Solution is to define a new attribute in request - get RM to return either those which are being used or all the ones in the database 2 (JP, 25/08/02; v0.02-0.05) - incorrect calculation of availability; location available tag dependent on case used in database (if available is "y" not available is returned). 1 (SG, 08/02; v0.01-0.05) - localhost not added to list of permitted hosts when installed with JDOM beta 8; causes socket crash on access. FEATURES FOR FUTURE RELEASES Support for explain request Improved logging REQUIRED LIBRARIES The Angel RM requires that the following .jar files are in the classpath of the user running the socket service or in the command line used to call it: a2j (if using Z39.50 client/server - distributed with jzkit) JDOM - tested with beta 7, beta 8 jzkit (if using Z39.50 client/server) log4j.jar (if using Z39.50 server) xalan - must be version 2.3 or later; tested with 2.3.1, 2.4.1 xerces.jar - jtidy (if using openurl client); tested with 04aug2000