CHANGE HISTORY UPDATED: 20011-07-06 - Changed Contact (name) element to ContactName - UsageDateRange - add ReportName as sub-element so usage date range can be provided for each report supported - set maxOccurs='unbounded' - ServiceNote - set maxOccurs='unbounded' - Alert - set maxOccurs='unbounded' - TestServerInstructions - added as a new element under "Registry" to capture the instructions to developers The SUSHI Server Status schema is used to report on the current configuration and status of the SUSHI Server. The 'Registry' element describes the configuration and set-up details for the client. The 'Status' element gives the current status of the server. The Content Provider. Details of a person to contact. Details for the Vendor or Customer. Name of the organization. The ID by which this organization is known by the content provider. In the case of the customer, it is the CustomerID as used by the content provider. The full name of the platform. e.g. 'EBSCOhost Research Databases' The 'Platform' value that appears in COUNTER reports. e.g. 'EBSCOhost' Information that pertains to the configuration of the SUSHI Server. This is also the same information that would be expected to be found on the SUSHI Server Registry. Information about the current SUSHI Status The URL for the production version of the SUSHI Service The URL for the test version of the SUSHI Server. The URL for the SUSHI Status Report web service. Who to contact with questions about configuring a client for this platform. Detailed instructions for clients wanting to use this server. Detailed instructions for client developers wanting to use this server in test mode. A description about the Platform's expectation for the RequesterID element when sending a SUSHI Request to the production server. e.g. does the client need to request a special identifier, or would then send the customer ID, etc. A description about the Platform's expectation for the Customer ID element when sending a SUSHI Request to the production server. e.g. does the client need to request a special identifier, or would then send the customer ID, etc. Description of the type of security imposed by the server. The list of COUNTER reports supported by the production server. The date and time when the registry information was last updated Clients will use this information to determine if they need to refresh information they have on file for the platform. These elements provide information on the current status of the server. Optional text that clarifies the state of the server. The overall dates of usage data available on the server. A repeating element of one per report. An optional note that is intended to alert the client about changes in the usage data. This alert would be used to inform the client that a prior month's usage data had been updated and suggest that they re-request that month's usage. A true/false flag that indicates if the server is currently active and able to accept requests. This true/false attribute is used to indicate if the production SUSHI server requires the SUSHI client to IP authenticate. This true/false attribute is used to indicate if the production SUSHI server requires as username/password at the service level (SOAP), or has implemented some other custom SOAP extension that must be accomodated by the client. The list of COUNTER reports supported by the production server. The official name of the COUNTER report as used in SUSHI Requests, e.g. JR1 The full name of the the COUNTER report e.g. Full text requests by month and journal The time period representing the usage data available on the server. Indicates the report the usage date range applies to. The official name of the COUNTER report as used in SUSHI Requests, e.g. JR1 The is the BEGIN date that can be used in a SUSHI Request that will get results. Use the first day of the month. The is the END date that can be used in a SUSHI Request that will get results. Use the last day of the month. The client will use this value to determine if the server offers any new usage since the previous request for a report and thus can delay the actual SUSHI request until new data is available to harvest.