Pure is an international product. The activities of the Dutch Pure User Group (PUG-NL) are therefore primarily aimed at introducing improvements and monitoring of issues specific to the Dutch market:
- The PUG-NL provides input of specific Dutch improvements in the Pure development roadmap, based on demand and developments within their own organizations, but also in (cooperation) projects of national organizations, clients and funding bodies such as Surf, UKB, VSNU and NWO .
- For improvements which are included in the development cycle of Elsevier, planning and development are monitored by a delegation of the user group, in the common interest.
- If required by the development process, a delegation of the PUG-NL will be tasked with testing new features.
- Any issues which then come to light, are prioritized and monitored in addition to all other registered issues and improvements.
Some issues and improvements are better addressed internationally, which means participation in an international special interest group (SIG) is required by one or more PUG-NL members. This relates to functionality that surpasses the national interest, or in which only a small group of Dutch users share interest, in which case collaboration with fellow universities abroad is important for meaningful implementation.
Process / organization PUG-NL
The current method of PUG-NL consists of a quarterly plenary meeting of all members, in which Pure improvements and issues are discussed. The (rotating) presidency of the group consists of three people responsible for organizing the meetings, the contact on behalf of the PUG-NL with Elsevier, and driving the improvement/issue schedule.
The improvements and issues ranges are divided into ten themes, controlled by two or three specialists who monitor improvements and messages by topic. Major improvements (such as the implementation of the SEP / KUOZ, Dutch counterpart of the REF) should be started in the form of a project, where a representation of the Dutch user group will be designated as a project team members. These representatives relay specifications to Elsevier and test on behalf of all participants. Progress is monitored in the usergroup meetings.
Using this method, it may occur that the time investment of members project into the PUG is greater than would be expected from the perspective of their own organization.
The PUG-NL participants currently mainly communicate via a (customer accessible) wiki environment hosted by Elsevier. The wiki has the advantage that we can link easily to all kinds of information and help desk system (JIRA) Elsevier.
In addition, the usergroup maintains the PUG mailing list, which is accessible only for Dutch customers of Pure. Given nature of the discussions and the need to refer to (internal) information on the Elsevier Wiki it is not practical to have non-customers use this mailing list.
Besides contacts with Elsevier the usergroup maintains contactswith other organizations that are stakeholders in the development or use of Pure. We are currently looking for ways to formalize and structurize these contacts.
The board of the PUG-NL is formed by a rotating presidency. At present, it consists of:
Ria van der Velde (UMC Utrecht)
Marijke Folgering (RUG)
Nick Veenstra (TU/e)