Metis Examples
This section contains examples of the XML files that Metis generates "behind the scenes" as its servlets are used to create users, groups, roles, events, and workflows.
- Metis User: All user information is stored in a user XML file. This file defines user information for the director of the Metis project. The password has been changed to protect the innocent.
- Metis Group: All group information is stored in a group XML file. The ids referenced by the users or roles elements select specific Metis users or roles to be associated with the group.
- Metis Role: All role information is stored in a role XML file. This file defines the editor role for a peer review process. This role is dynamically bound and, as such, its player element is empty. If the role had been statically bound, the player element would reference a particular user or group id.
- Metis Event: All event information is stored in an event XML file. This file defines a submissionReceived event for a peer review process. The event has attributes to store information about the submission such as its title and author list. It also contains contact information for the contact author and associates an id with the submission. The id attribute is a key attribute. Key attributes are explained in the Metis overview.
- Metis Workflow: All workflow information is stored in a workflow XML file. This file defines a workflow consisting of two events. The events are referenced by their id. The first event is the submissionReceived event defined above. Several actions are associated with this event, including sending an e-mail message to the administrator of the digital library, downloading the submission (using the event's URL attribute), and dynamically binding a role based on the event's area attribute.