Step 2: Create Events [web|gui]
This part of the tutorial steps you through the process of creating the events for the peer review process. Event creation typically will be an iterative process that will require the input of multiple stakeholders. In this step, we provide only minimal information about the purpose of each event. The contribution of each event will become more clear in Step 3 and Step 4 of the tutorial as we construct workflows and associate actions with their events.
1. Click on the Events tree node in the leftmost Metis Tree panel. If this is your first time using the event editor, the List panel will be empty. Otherwise, there will be a list of events to choose from. Clicking on any of the existing events will bring up the Event Editor in the rightmost panel. This editor displays an attribute table containing the attributes of the event.
2. Click on the Add toolbar button. A new event (New_Metis_Event_1) will appear and the Event Editor will display details about this new event. Initially, there will be only three attributes in the attribute table namely, metis_time_stamp, metis_event_name and (New Attribute Here). The first two attributes are default attributes used internally by Metis. You should never edit them or delete them. The third attribute is a placeholder to add information about a new attribute. This placeholder attribute is never actually saved into the repository unless you edit its information. To create addtional placeholder attributes, click the Add Attribute button.
3. In the Event Name text field, type submissionReceived. Type id in the Name column which currently contains the value "(New Attribute Here)". Leave the Default Value field blank, click the Is Key checkbox and then click the Add Attribute button. As mentioned above, this button will create a new placeholder attribute for editing. To save your changes, click the Save Repository button. If you need to remove an attribute, select it and then press the Delete Attribute button.
4. Add the following additional attributes to the submissionReceived event: area, authors, contactName, contactEmail, title, and url. Only the id attribute should have its Is Key box checked. The snapshot below shows a part of the interface after you have entered all the information for the submissionReceived event.
5. Save the event by clicking on the Save Repository button. The name of the event will change inside the List panel to reflect the new name: submissionReceived. If at any point you want to undo your changes, you can click on the Revert All Changes button. However, you cannot undo your changes after you have clicked the Save Repository button. In fact, the Revert All Changes button is enabled only after a change is made to an event's properties.
6. Using the table below, create the rest of the events. Each event has an id attribute that must have its Is Key box checked. No other attribute needs to be key.
| Event Name | Attributes |
|---|---|
| submissionProcessed | id, url |
| actionEditorAssigned | editorEmail, editorName, id |
| reviewerAssigned | id, reviewerEmail, reviewerName, url |
| deadlineAssigned | deadline, id |
| deadlinePassed | id |
| reviewComplete | id, status, url |
| authorNotifiedOfSuccess | id, url |
| authorNotifiedOfRejection | id, url |
| authorNotifiedOfRequiredRevision | id, url |