Method and Apparatus for Project Management Field of the Invention.

[0001] The present invention relates to a method and apparatus for project management.

In particular, the present invention relates to a method and apparatus for the management of research activities and participants, especially in qualitative and mixed methods research.

Background Art.

[0002] Qualitative and mixed methods research is a general term to describe a multitude of methodologies and research practice designed to help researchers and practitioners in understanding, describing and explaining social phenomena within a real world context. Qualitative researchers study things in their natural settings, attempting to make sense of, or interpret, phenomena in terms of the meanings people bring to them. Qualitative and mixed method researchers use data gathered through interviews, focus groups, surveys, documents, photos and videos to help them develop models and theories to describe social and psychological issues. The methodology is used in a variety of fields, but most particularly in social, health and medicine, cognitive and psychological, education, organisational, business and management and market disciplines.

[0003] The management of qualitative and mixed methods research has historically been complex and inefficient, particularly when collaborative research is conducted in large team environments or on multi-site research projects. In these situations, collaborative research has been achieved through the use of electronic spreadsheets, email or file transfer services (such as FTP servers, network storage devices or USB drives sent through the mail). These processes are insecure, have limited control of access and storage of sensitive files, do not provide an auditable record of all research related decisions and have high levels of task duplication.

[0004] Thus, there would be an advantage if it were possible to provide a system for secure collaborative project management and data storage for qualitative and mixed methods research and researchers.

[0005] It will be clearly understood that, if a prior art publication is referred to herein, this reference does not constitute an admission that the publication forms part of the common general knowledge in the art in Australia or in any other country.

[0006] Throughout this specification, the term "comprising" and its grammatical equivalents shall be taken to have an inclusive meaning unless the context of use indicates otherwise.

Summary of the Invention.

[0007] It is an object of the present invention to provide a method and apparatus for project management which may overcome at least some of the abovementioned disadvantages, or provide a useful or commercial choice.

[0008] In one aspect, the invention resides broadly in a computer-implemented method of managing collaboration comprising the steps of:

Providing electronic storage means for the storage of a data set related to a project;

Providing an electronic interface adapted to allow a plurality of users to gain access to the electronic storage means;

Allowing one or more of the plurality of users to modify the data set related to the project to the electronic storage means;

Providing computational means associated with the electronic storage means, wherein the modification of the data set results in the computational means calculating one or more parameters relating to the project; and

Communicating the one or more parameters to one or more of the plurality of users in order to establish updated project goals.

[0009] In another aspect, the invention resides broadly in an apparatus for managing collaboration, the apparatus comprising:

Electronic storage means for the storage of a data set related to a project;

An electronic interface adapted to allow a plurality of users to gain access to the electronic storage means and modify the data set;

Computational means associated with the electronic storage means, the computational means being adapted to calculate one or more parameters relating to the project; and

Communication pathways adapted to communicate the one or more parameters to one or more of the plurality of users in order to establish updated project goals.

[0010] In another aspect, the invention resides broadly in a computer-implemented method of project management comprising the steps of:

Providing, in computer network architecture, electronic storage means for the storage of a data set related to a project;

Providing, a computing device having a processor with memory and a display for generating and display of an electronic interface adapted to allow a plurality of users to gain access to the electronic storage means;

Allowing one or more of the plurality-of users to modify the data set to the electronic storage means using communications pathways between the computing device and the computer network architecture;

Providing computational means associated with the electronic storage means within the computer network architecture, wherein the modification of the data set results in the computational means calculating one or more parameters relating to the project; and

Communicating, via the communication pathways, the one or more parameters to one or more of the plurality of users in order to establish updated project goals.

[0011] In another aspect, the invention resides broadly in an apparatus for project management comprising:

Electronic storage means associated with computer network architecture, the electronic storage means adapted to store a data set related to a project;

A computing device having a processor with memory and a display for the generation and display of an electronic interface adapted to allow a plurality of users to gain access to the electronic storage means;

Computational means associated with the electronic storage means within the computer network architecture, the calculation means adapted to calculate one or more parameters relating to the project after modification of the data set; and Communication pathways between the computing device and the computer network architecture to communicate the one or more parameters to one or more of the plurality of users in order to establish updated project goals.

[0012] In yet another aspect, the invention resides broadly in an apparatus for project management comprising: \

Computer network architecture adapted to host electronic storage means for the storage of a data set related to a project;

One or more computing devices having a processor with memory and a display connected to the computer network architecture;

A calculation engine associated with the computer network architecture, the calculation engine adapted to calculate one or more parameters relating to the project; and

Communication pathways adapted to communicate the one or more parameters to one or more users.

[0013] It will be understood that the term "collaboration" may be used to refer to any suitable collaborative activities. For instance, the collaboration could be part of a research project, construction project, educational project or the like. The participants in the collaboration, and therefore the users of the method may be one or more universities, one or more individuals, one or more private companies, one or more government departments or the like, or a combination thereof.

[0014] It is envisaged that the participants may have the same or different roles in the collaboration. For instance, some of the users may be involved in the collection of raw data relating to the project, and/or entry of the raw data into the data set. Some of the users may be involved in the analysis and manipulation of the raw data. Still further, some users may be involved in supervision of the project and of other users. Finally, some users may be involved in the review of the data. Thus, it is envisaged that the data set may contain one or more of raw data, analysed data, supervised data and reviewed data.

[0015] The users may have the same or different roles in different collaborations and the system will therefore preferably be capable of distinguishing between users and their ensuing rights within the system based on the particular collaboration. [0016] The data entered into the data set may be of any suitable form. For instance, the data may be numerical data, written data, results of trials and experiments, financial information (including expenditure, cash flow, taxation and revenue information), results of literature searches, results of statistical analysis, results of peer review, comments, calendar entries, photographs, drawings, graphs and charts, user or test subject names and contact details, questions and/or corrections by other users and so on, or a combination thereof. The data may be manually entered into the data set, or may be in the form of electronic documents (such as electronic spreadsheets, word processor documents, presentations or the like) or paper documents reproduced in electronic form (such as scanned copies of publications, articles, and so on).

[0017] The data set may also include a communication capacity, such that users may communicate with one another, for instance in real time (by video link, voice over Internet protocol (VOIP), instant messages), or via text messages or email messages targeted to one or more other users. In some embodiments of the invention, users may be able to enter data into the data set directly from a suitable device such as, but not limited to, a mobile telephone, portable computing device, camera, medicine dispenser or the like. This may be achieved using any suitable technique, although it is envisaged that users may be provided with a data entry interface which is distinct from the electronic interface. Preferably, the data entry interface allows only for the entry of data into the data set, although it is envisaged that the data entry interface may also be provided with some other limited functionality. The data entry interface may be provided on a display (such as a screen) on a device. Alternatively, in some embodiments of the invention, a mobile telephone or portable computing device application ("app") may be provided to users that allows data to be entered directly into the data set.

[0018] In a preferred form, the data set for a collaboration will typically include all data in relation to the collaboration at a particular time. Any change to the data relating to the collaboration that is saved in the at least one database will typically update the data set, producing a new data set after the change.

[0019] The electronic storage means may be of any suitable form. For instance, in a preferred embodiment of the invention, the electronic storage means may include one or more servers or databases on which the data set is stored. In embodiments of the invention in which more than one server is present, it is preferred that the multiple servers are in electronic communication with one another.

[0020] The electronic storage means may include a single data set related to a single project. Alternatively, the electronic storage means may include a plurality of data sets related to a plurality of projects.

[0021] The electronic interface may be of any suitable form. It is envisaged, however, that the electronic interface may be provided on one or more computing devices. In particular, it is envisaged that the electronic interface may be provided on a machine- or human-readable display on a computing device. Any suitable display may be provided, such as a screen . Any suitable computing device may be provided, such as one or more computers connected to one another in a network, such as a local area network (LAN).

[0022] Alternatively, the electronic interface may be accessed remotely through any suitable electronic computing device. For instance, the electronic interface may be provided by radio, Ethernet, Internet, satellite signal, cloud computing, fixed phone line or the like (or a combination thereof) to a computer, PDA, mobile telephone, computing tablet device or the like, or a combination thereof. In this way, it is envisaged that users in locations remote from one another may access the data set.

[0023] The electronic interface may provide access to the data set using any suitable technique. In some embodiments, the electronic interface may include one or more security features to prevent unauthorized access to the data set. For instance, an authorized, user may be provided with a password or access code that may be entered into the electronic interface in order to gain access to the data set. In some embodiments, all users may be provided with the same password or access code to access a data set related to a particular project. Alternatively, each user (or group of users) may be provided with a unique password or access code to gain access to the data set.

[0024] A user may obtain a password or access code a number of ways. For instance, project members may be identified in the data set and each member (or group of members) may be assigned a password or access code. Alternatively, a person or group may be invited to become a user, and may receive a password or access code on acceptance of the invitation. Still further, a person or group may apply to become a user, and may be provided with a password or access code once the application has been assessed. In some embodiments, it is envisaged that a person or group may be able to obtain a password or access code on payment of a fee (for instance, a licensing fee).

[0025] In some embodiments of the invention, a user may access the electronic interface without activating the computational means. For instance, a user may be able to access the electronic interface and modify data in a local setting, for instance, when the user is unable to connect to the Internet. However, when the user next connects to the electronic storage means via the electronic interface, the data modified in local setting (or "offline" mode) may then be automatically or manually entered into the data set.

[0026] The electronic interface may include one or more electronically fillable forms into which data may be entered. Data may be manually entered into all electronically fillable forms, or the entry of data into some forms may automatically populate data fields in other forms. Data may be entered manually using any suitable technique, such as keyboard entry, voice recognition, selecting options (for instance, by using a mouse, pointer or touch screen) from one or more lists, drop-down menus, calendar entries, check boxes (for instance, to register the completion of a task), pop-up menus or the like, or a combination thereof.

[0027] In a preferred embodiment of the invention, the electronically fillable forms may include one or more fields into which data may be entered. It will be understood that the exact nature of the fields will be dependent on the nature of the project and the type of data that has been collected. For example, the fields may prompt the entry of certain information and/or information in a particular form or may allow free-form entry of information.

[0028] Still further, data may be entered into the data set in machine readable format, and converted into a human-readable display (for instance, by automatically populating the one or more electronically fillable forms) or vice versa or one to the other and back again as desired or required. Any suitable machine readable format may be used, such as the entry of data in machine code, the use of character recognition or the like, or a combination thereof.

[0029] The data entered into the electronically fillable forms may be converted into a format that is more readily readable by a user. For instance, the electronically fillable forms may be converted into a written report. Alternatively, the electronically fillable forms may be converted into a graphical representation of the data set, such as one or more graphs or charts (including pie charts, Gantt charts or the like).

[0030] It is envisaged that the electronically fillable forms may also inform a user of what tasks they are required to complete. The electronically fillable forms may also include deadlines by which a task must be completed and/or a list of collaborators (and the tasks they are required to complete).

[0031] The electronic interface may include one or more buttons adapted to perform certain tasks. For instance, buttons may be provided to save the data set so as to ensure that changes to the data set are retained. Buttons may also be provided for any other suitable operation, such as indicating the completion of a task and so on.

[0032] In a preferred embodiment, the electronic interface further includes one or more links to other data in the data set. These links may be, for instance, hyperlinks to allow a user to navigate through the data set. The hyperlinks may lead a user to a new part of the data set, generate a pop-up menu, or the like.

[0033] In it envisaged that, in some embodiments of the invention, different users may have different levels of access to the data set. For instance, some users may be provided with a level of access that allows them to enter, delete or manipulate data in the data set. Alternatively, some users may be provided with access only to view, but not edit, the data set. It will be understood that the level of access provided to individual users (or groups of users) will vary depending on the project, and the number and type of users involved. However, it is envisaged that at least one user per project may have high level access to the data set (for instance, to add or remove users, to modify data, send messages, set level of user access and the like) so as to act as an administrator of the data set.

[0034] In some embodiments of the invention, a user may be able to access the electronic storage means and modify the data set by adding new data and/or view the data that has been entered into the data set. The amount of data that a user may view may vary depending on the nature of the project. For instance, a user may be able to view all data in the data set, all data except classified or sensitive data, the data added to the data set by only selected users, or only the data added to the data set by the user themselves. It is envisaged that a user's access to the data in the data set may be set by the administrator, and may change depending on the development of a user's role in the project.

[0035] The modification of the data set may be of any suitable form, and it will be understood that "modify" in the present context is not intended to be limited to merely the entry and manipulation of data in the data set. It is envisaged that, in the present invention, the term "modify" is intended to refer to the entry of data into the data set, the manipulation of data in the data set, the deletion of data from the data set, the analysis of data in the data set, the review of data in the data set, communicating with other users regarding data already entered or data to be entered in the future, setting deadline for the entry of data and the like. Again, it will be understood that the exact modifications to be made to the data set will be dependent on the project.

[0036] In some embodiments of the invention, all of the users may have access to the entire data set. However, in an alternative embodiment, a user's (or group of users) access to the data set may be limited depending on the nature of the project and the user's need or clearance to access the entire data set (or, for instance, sensitive or classified portions of the data set). In this way, confidentiality of the data set may be maintained.

[0037] It is envisaged that, as new data is entered into the data set, and/or as new or existing data is manipulated in the data set, the computational means will calculate one or more parameters relating to the project. Any suitable parameters may be calculated, including numerical results (for instance, through the entry of data into mathematical equations), written results (e.g. the production of a written report, or completion of an electronic form or checklist, based on data in the data set), new deadlines associated with the project, new tasks required to be performed by users or groups of users, the repetition of tasks already conducted (for instance, if the data is inaccurate or incomplete, or if newly-entered data contradicts data previously entered into the data set) and the like, or any combination thereof.

[0038] The computational means (or calculation engine) may be of any suitable form, although it is envisaged that the computational means/calculation engine may include one or more processors. The one or more processors may be physically associated with the electronic storage means, or may be located remotely from the electronic storage means but in electronic communication therewith.

[0039] The one or more parameters may be communicated to one or more of the plurality of users using any suitable means. In some embodiments of the invention, the one or more parameters are communicated via communication pathways. The communication pathways may include communicating the parameters by email message, text message, instant message, telephone call or the like, or a combination thereof.

[0040] While it is envisaged that the one or more parameters may be communicated to one or more remote devices, it is also envisaged that the communication of the one or more parameters may be achieved through the electronic interface. For instance, when a user accesses the data set through the electronic interface, the user may receive a message, audio or visual signal or the like, or a combination thereof, communicating the one or more parameters.

[0041] The communication received by the user may be of any suitable form. For instance, the communication may be a message indicating that the data set has been modified. The communication may also be in the form of a report, indicating the nature of the modification to the data set, the user who performed the modification and so on. Still further, the communication may alert one or more users to new deadlines or tasks associated with the project, and advise the user as to what action is required from them to comply with the new deadlines or tasks.

[0042] It is envisaged that a communication regarding changes in the data set may be sent to all users for a particular project. Alternatively, a communication may be sent to only some of (i.e. a portion of) the users (for instance, supervising users, users involved in the particular part of the project to which the modified data set relates, users for whom the modification of the data set creates new deadlines and tasks etc).

[0043] In some embodiments of the invention, a hierarchy of communications may be created for one or more users or group of users. For instance, communications that directly (or indirectly) effect a user or group of users (such as when a new task or deadline is created) may be sent with a high level of importance. On the other hand, communications relating to a change in the data set that does not impact, or has only a minimal impact, on a particular user or group of users may be sent with a low level of importance (or not sent at all). Any suitable number of levels of importance for communications may be used, and the actual number used is not critical.

[0044] There are a number of advantages provided by the present invention. These include the fact that the present invention is suitable for collaborative projects (such as qualitative and mixed methods research projects, or any participant (or subject based) research methodology), provides secure and encrypted data storage, allows access to the data set at all times, increases the efficiency of data collection, viewing and reporting^ and allows users to work on data without adversely affecting workflow productivity and efficiency.

[0045] In addition, the present invention promotes independent team activity and accountability whilst enabling executive level access and control. It provides a current snapshot of project progress as well as specific details of individual participants or subjects. In addition, efficiency is streamlined through the ability to avoid task duplication associated with using disparate forms of communication and computer software.

Brief Description of the Drawings.

[0046] An embodiment of the invention will be described with reference to the following drawings in which:

[0044a] Figure 1-6 illustrate an electronic interface display according to embodiments of the present invention.

Detailed Description of the Drawings.

[0047] It will be appreciated that the drawings have been provided for the purposes of illustrating preferred embodiments of the present invention and that the invention should not be considered to be limited solely to the features as shown in the drawings. [0048] In Figure 1 there is shown an electronic interface display 10 according to an embodiment of the present invention. The electronic interface display 10 is the first screen or display that a user sees when the user connects to the electronic storage means via the electronic interface 10.

[0049] The display 10 shown in Figure 1 provides an overview of the user's projects 11, their completion status 12 and the number of tasks 13 awaiting the user's input. The display 10 includes a button 14 that allows a user to create a new project. Further, the display 10 includes a series of buttons, located in an area of the display 10 referred to as the dashboard 15 that allow a user to access the data set related to a particular selected project 11.

[0050] In Figure 2 there is shown an electronic interface display 16 according to an embodiment of the present invention. The electronic interface display 16 holds and displays information pertaining to the administration of workflow and tasks and users that have been assigned to stages of the project and particular tasks. It is envisaged that, once the project has been initialised, it will not be necessary to interact frequently with this display 16 unless there is a change in team responsibility and assigned workflow stages.

[0051 J In Figure - 3 there is shown an electronic interface display 17 according to an embodiment of the present invention. The electronic interface display 17 is the dashboard for a particular project and contains all relevant information associated with the project. The dashboard lists task and responsibilities that have been assigned to a user. In the embodiment illustrated in Figure 3, the dashboard displays:

[0048a] Participant stages and tasks 18 relevant to the assigned stages;

[0048b] A calendar 19 which shows upcoming or previous appointments, interviews or other scheduled tasks;

[0048c] A list of team members 20 and their responsibilities and assigned stages; and [0048d] A notification information panel 21.

[0052] The participant stages and tasks section 18 lists participants that have entered a workflow stage that has been assigned to a user and acts like as a list of tasks to be completed. A drop down menu 22 allows a user to define the view of the Dashboard to display one assigned stage or all of the assigned stages.

[0053] Once all tasks 18 within a stage have been completed, the drop down menu 23 is used to move the participant to the next stage. If a participant is not assigned to the subsequent task, the participant will disappear from the list 20.

[0054] In Figure 4 there is shown an electronic interface display 24 according to an embodiment of the present invention. The electronic interface display 24 allows a user to access a pop-up menu 27 in order to display and edit all information pertinent to a participant and the project. The information is accessed by clicking on the hyperlinked name of a participant 25. The participant edit function houses a further five tabs 26 including:

Participant Data

[0055] Participant data stores all information relevant to the participant including contact details and specific demographic or project specific data. Details can be amended or added to the participant throughout the course of the project.

Tasks

[0056] Tasks list displays workflow stages and tasks associated with the project.

Information in this tab is static.

Appointments

[0057] The appointments tab is intended to store date and time data for participant interviews and meetings. Dates and times that are stored in the appointment tab will be displayed on the calendar in the dashboard. Dates and times will also be logged in the history. Notes

[0058] Notes are used to record any additional information about the participant.

Information can include interview notes, information provided after the recording, notes about attempted contact and strategies used and so on.

Files

[0059] Files are used to record collected data from the participant. Files can include consent forms, digital interview sound files, transcriptions and any other information attributable to the participant.

History

[0060] History provides a detailed account of all actions that have recorded against the participant, when actions occurred and who performed the action. Information ^' can be used to ascertain enrolment difficulties, troubleshoot problems and provide a complete project audit.

[0061] In Figure 5 there is shown an electronic interface display 28 according to an embodiment of the present invention. The electronic interface display 28 is the participant page shown in the background of Figure 4.

[0062] In this display 28, a user can add a new participant to the project by clicking on the "participant create" link 29.

[0063] A user may elect to add a single participant if using a snowball enrolment technique or if the user is unsure of the potential participants. By clicking on the "participant create" link 29, a blank Participant Edit Pop Up will appear. A user will fill in the necessary details, click save and the participant will appear in the participant window 28.

[0064] Alternatively, a user may elect to add multiple participants, or a group or list of participants at the same time.

[0065] In Figure 6 there is shown an electronic interface display 30 according to an embodiment of the present invention. The electronic interface display 30 illustrates the manner in which a file (such as a sound file, word processor document, spreadsheet, picture, photograph and so on) may be attached to a participant and stored in the data set. Once a file is added to the data set, it is safe from loss, deletion or removal. Adding files occurs through the Participant Edit Pop-Up. To access this page, a user clicks on the participants name 31 (or 'Edit' in the Participants Page shown in Figure 28.

[0066] To add a file, a user clicks on the Files tab 32 to display a list of files 34 already added. A user will then be able to choose a file to add from a computer, sound recording device or the like. Once selected, a user will click a button mark 'Upload' 33. The file will upload and display a graphical progress bar. Once complete, the user will be returned to the File window where he or she can view the added file.

[0067] Further embodiments of the present invention are shown in the attached Annex.

[0068] Those skilled in the art will appreciate that the present invention may be susceptible to variations and modifications other than those specifically described. It will be understood that the present invention encompasses all such variations and modifications that fall within its spirit and scope.

ANNEX

Quadraut Overview

Intention

Features

History

Using This Document

This document aims to provide detailed specifications and functionality for design and development of Quadrant. The document is not intended to provide technical representation of Quadrants features, but to be used as a guide in development and design. The document charts all intended functionality desired in Quadrant and provides a guide for the accompanied schematic and page layout diagrams.

The document is structured to provide self explanatory text to the Page Layouts. A Page Layout refers to a distinct web-page within Quadrant and is represented by an individual number. Distinct functions within each page layout contain unique identifying numbers which correspond to schematic diagrams and/ or explanatory text within this document. In some cases, a Page Layout reference number may not have an accompanying schematic diagram, in which case explanatory text is provided. In most instances, explanatory text and schematic diagrams will exist.

Please Note: Due to the fluidity of this document, identifying numbers maybe non sequential and/or omitted.

Page and Information Hierarchy

This chapter presents the information architecture of Quadrant. The chapter presents, data and storage pivots, project users and rights, workflow and task concepts and an overview of information displays.

Chapter 0 - Website Flow Through and Information

This chapter provides information relating the overall website flow and navigation.

Chapter 1 - Unique Pages/ Elements

This chapter provides detailed information on Page Layouts and their accompanying functions.

Information is presented by stating the primary object of the page or function and its' accompanying primary or secondary functionality. Functionality is listed in an hierarchical order from most important and used functions to least used and obscure functionality. This is listed to assist design priorities and reinforce the intended main functions of each Page Layout.

Help text is also presented within for each function.

Chapter 2 - Global Notification and Feedback

This chapter presents system notification features available to the user throughout Quadrant- Notification and feedback systems should be recognisable but discrete and enable communication to the user regarding processes and sub- processes that are occurring within the system, either from user input or from dient/server processing.

Chapter 3 - Global Icons and Related Assets

This chapter presents iconography and user interface functions available in Quadrant.

Chapter 4 - Global Popup Functionality and Data Inputs

This chapter details consistent features that are used in data input processes in Quadrant. Features presented in this chapter are populated throughout Quadrant.

Chapter 5 - Quadrant Administrator

This chapter presents information pertaining to administrative and management features of Quadrant, including project and user statistics, content management systems and financial systems. The Quadrant administration feature is developed for owner and operators of Quadrant.

Page and Information Hierarchy

Quadrant Is developed to assist in qualitative project management, analyse and collaboration.

Users - Research programs - not institutional

MVCArchieture.

Storage information - revolves around participant

Personal information

User - quadrant administrator, users,

0. Website Flow Through and Operations

Website Framework

0.1 Personal - Trie personal page allows users to adjust personal settings that are used across multiple quadrants - such as User Login and Personal Details (e.g. blurb, institutional details - email details)

Country and timetone - for email notifications

Calenderand ICAL sharing

ettings - hare Appointments Or (Default)

Help Text: (You will s»li be able to view your appointments and details but others will not) Share Appointments and Details

Notification Options:

Restrict External Notification options - e.g. Ho emails notifications

Change Notification Email

Payment and silting Details

Global Private Files and Calender and Notes

New project -

When setting up a new project - incorporate project codes and fields of research in E.g. Palliative care, Haematofogy, Sociology, Psychocology, Market Research, Country? to allow categorisation of projects an the front end website and the development of a database that can be used for future data mining,

Archive Project

Delete Project from Quadrant servers

signed in - link to Name

List of Current Projects and Archived Projects

0. Login Process

0.2 Initial Project Setup

0.3 Subsequent Projert Setup

0.4 Initial User Setup

0.S Subsequent User Setup

1. Unique Pages/ Elements

Initial Landing Page

Purpose: the initial landing page provides the user an overview of all current projects, their completion status and tasks requiring input to which they have been assorted.

Primary function. To allow users to navigate to their projects and to provide an overview of each projects status. Secondary Function: To provide information to users regarding tasks required for each protect.

1.1.1 Project Completion Function - provides the user with an percentage overview of the project. Completion rate is calculated by SUM OF AIL STAGES COMPLETED/ (PARTICIPANTS IN WORKFLOW STAGES) 100

1.1.2 Awaiting Tasks - provides the users with the number of awaiting tasks that have been assigned to them and require work input.

Project Dashboard

Purpose: This page dtspfays aft active and archived projects tagged with information about the respective project The dashboard is the primary page in which most work and interaction with each participant occurs. The dashboard displays a set up of unique elements that correspond to most of the mam functions in Quadrant, including Workflow view; user and Messages, Participant Edit, Calender and reports.

Primary Function: The primary function of the dashboard is to aBow users that have been assigned to a workflow stage, easy identification and options to allow them to complete then" assigned tasks. Most work associated with the research process wH occur in the dashboard.

Secondary Function: To allow users to view overall progress of the reports, upcoming appointments and to communicate to other users.

1.2.1 Tasks/ Notifications Workflow: The Work-flow V e provides an overview of how the project is progressing with respect to the selected participants of the qualitative research. It is a vita! area of a Project Management system to incorporate, indications/ charts/ progress bars etc to have a quick overview of the progress of the project. Hence the Work-flow View is designed for this specific purpose. Depending on the type of Work-flow, the Wort-flow process is customizable to be able to add, append or remove a task within the process. Further individual tasks within work-flow can be assigned to individual users.

1.2.1. l participant Edit - allows the user to edit fields associated with the user . articipant edit can also occur in oataview.

1.2.2 User Messages - The user page is designed to allow users with to view at) users and their designated user groups within a project, view their project rights and communicate with other users.

UA Calender - allows the user to view upcoming events, schedule appointments and shift between project and Quadrant wide view

1.2.5 Reports - provides the user the ability to view user generated reports and an overview report.

Data View Page

Purpose: oataview allows users to view, sort, search and perform operations on individual and buik participant tt is used to input and management the purposive sampling com ponent of Qualitative research Da aview allows users to view and manipulate user views and change workflow statuses of individual or bulk participants. Primary function: Dataview primary function is to display bulk information about participants that have been uploaded and to be able to sort and move those participants into the workflow.

Secondary function: Assigning user rights and developing reports for views in other screens.

Default Sort View - Data that is entered through a either bulk upload is sorted in order of upload. User arriving at the Dataview will always be displayed with the previous search with an onscreen notification to remove any sorts or filters that have already been applied.

13.1 Search Menu - The search menu allows for users to instigate a complex search with hierarchical categories of sorting.

13.1,1 Complex Sort - Complex sort allows users to developed more comp licated searches based upon a hierarchical searching structure. Users can elect to save the search as a custom name or use the automatically stored name.

Help Text: Complex sea rch enables you to categorise and order your participant data. You can change the hierarchical category by dragging and dropping individual searches.

13.2 - Add Participant - Add participant pop up a (tows the user to add multiple a i ipants or single participants, it also allows users to append

once dick odd participant o ens a new row in the oots ew for sers to directly enter a participant into Dataview Does row disappear if not added to?

Help Text (Single Participants): You may add new participants to an existing workflow tab or to a new workflow tab.

Help Text (Multiple Participants): you may add multiple participants to an existing workflow or a new tab. Multiple participants can be uploaded using a CSV or Microsoft Excel file. Quadrant will attempt to match fields in the upload file to pre-existing fries. Adding to another tab may help rf there are multiple large participants cohorts with distinct search criteria.

1.3.2. l - F»eld Match Participant Data - Allows user to intuitively match data input to new or existing categories at time of input. The function also allows user to Input data into additional worksheets.

13.4 Sort Menu Column view - al lows a user to basic sort on functions in the column such as atphabettcaily. numerically and to restrict viewing to distinct or non nufl values.

13. More Options - allows users to cut/ copy or delete selected participants from the Dataview.

13.6 Return to Previous View - return to previous view loads the previous search or sort settings. It is an 'undo' function for users

13.7 Remove Ait Filers - allows users to remove any filters and sorts attached to the current Dataview. ft allows use rs to return to the dat a as per their user credentials and initial upload.

13.9 Workflow Operators View- allow users to categorise and sort participants based upon individual workflow completion. Users can drill do wn to individual workflow tasks for mo re detailed control of the Dataview.

13.9.1 -change Participants orkflow stage - allows users to change workflow stages of individual and bulk participants.

13.10 - Assign P rticipants to Work low - allows users to quickly assign archied participants into the workflow. Function also enables individual or bulk changes to workflow stages. Future Functionality:

Fo us Groups - increased ability for users to organise and group participants for enrolment in focus groups and other group related data gathering activity Requires ability to group participants and store one set of dab across multiple participants. Participant Edit Page

Purpose: The Participant Edit page presents alf information stored for a participant and contains alt functions that a user can access to complete their workflow for a participant. Most information, unctions and work will be completed between the Participant Edit Page and Oashboard Page.

Primary Function: For users to record and store interactions and information relating to work that has been completed with a participant.

Secondary Function: for users to view and edit participant data and fields.

1.4.1 Participant Details - provides the user the option of viewing and editing participant detail fields within the database.

1.4-2 Workflow Stages and Tasks - provides the user with an overview of Workflow Stages and Tasks that need to be completed and the ability to view and add fBes, notes and appointments to such tasks.

1.43 Documents - provides the user with a list of current and previous appointments, notes and documents assigned to the participant "

Future Functionality:

Transcribe - additional services.

VOIP - includes the ability to record and call straight from the website using VOIP technicalities. This includes an automatic record function so users can conduct an interview and save directly to Quadrant . (Explore XMPP protocol, Google Talk, Linphone, Doodle, Sip Provider and Server)

Analyse - Permits the user to analyse data transcription or data contained

Calender Page ^

Purpose: The calendar page provides a representation of scheduled interviews and appointments across one or multiple projects.

Primary Functionality: to allow an overview of date related activities across single or multiple projects.

Secondary Functionality:: to allow users to schedule appointments and assign such appointments to a workflow stage and/or participant.

1.5.1 - Add Appointment - aiiows a user to add an appointment within the calendar window. A user can attach the appointment to a participant, workflow or as a non-attached appointment.

Administration Page

Purpose: The Admin page contains a set of functionalities that control features and project related information within Quadrant. The administration page lists of aSI features and options to can be implemented within Quadrant. Primary Functionality: to allo administrators to enrol and edit users and edit workflow stages and tasks. Secondary Functionality: To ailow users to set or turn-off particularly functionality.

1.6.1 -Options - Options allows users to control communication and behaviour settings (such as display warning that was previously switched off) for projects and quadrant.

Help Text: The option page allows you to control how you received notifications and email from Quadrant. You can limit message settings and toggle warning display messages from here.

Help Text (Apply to all my projects): Applying this setting to ail projects overrides any individual project settings.

1.6.2 Project Tools - Project Tools allow an administrator to Export Data, Archive a Project and commission a new project.

1.6 Λ Project Tools - Export Data -Allows an administrator to export the entire project or component of a project.

Help Text: This option allows you to export project data stored in data. You can elect to export the entire contents or selected files.

Help Text Archive: You can elect to archive your project. Archiving your project stores the project on Quadrant servers. During your project subscription period you can bring a project out of archive into a current proj ect. To delete data of the Quadrant Servers visit the Quadrant Administration area.

1.G.3 Assign Project Workflow and Tasks - Allows an administrator to edit and define workflow stages and tasks and view users that are assigned to a workflow. The premise is of User Group Assign is that members belong to the group are responsible for the workflow stage and component. User groups can still edit or view project workflows and data subject to appropriate user credentials

Help Text: This page you can determine the stages and tasks that are needed to complete your project and to assign user groups to each workflow stage. User groups assigned to a tage assume responsibility forthat stage and will be sent automatic notifications concerning events with the stage. Other users may be able to view and edit information within the workflow depending upon their user credentia ^l s. To edit user credentials go to the User Groups Page.

To change order of stages or workflows simply drag and drop items. You can rename workflows stages or task. You can edit workflow stages and tasks at anytime during the project.

Help Text Email Enrolled Users Once Activated: This function will send an email to enrolled members when a participant enters a particular workflow.

Help Text Impose Sequential Integrity of Workflow: This function forbids workflow stages or tasks to be completed before all precedin workflows and tasks have been competed.

Help Test Workflow Options: Notification Period - The Notification Period is t he estimated time needed to complete the corresponding task. By defining the notification period, users assigned to the particular role will receive a notification email once the notification period has expired.

Enforce Requirements -Enforcing requirements ensures that a completed workflow tasks has either a file, scheduled appointment or saved note attached to the respective workflow task. Users will not be able to finish the task without completing the required options.

Remove - This function enables you to remove a task from a workflow.

1.6.3.1 Assign Workflow - alfows users to assign appropriate credentials to allow a User groups to complete tasks to who have been assigned to a workflow in 1.6.3.

1.6.3.2 - View/ Edit Users - allows a user with appropriate credentials to view and edit users who belong to an user group.

1.6.3.3 Remove User Group - allows a user to delete a user group. This function removes any credentials an individual user may have by belonging to the previous group. It does not delete the users.

L6.3.4 Delete Workflow/ ask - Allows a user to delete a workflow. Deleting a workflow also removes any associated ta ks and assigned user groups.

1.6.3.5— Task Requirements— Allows an admin istrator to suggest an action that needs to be accompanied with a task. If the task is checked with an Enf orce Requirements, users must complete the action before completing the task. Administrator

Help Text -Enforce Requirements - By choosin 'Enforce Requirements' you are restricting the task to be completed untii the task has a particular action recorded. Administration users can override the requirement and set a task completed without needing to have an action recorded.

1.6.4 Project Users - A!lows an administrator to enrol, edit and remove access rights for users based upon a user group system. Groups are listed sequentially in order of user rights. A user must be assigned to a user group to access project resources, although a user can be enrolled and have no access to project resources.

1.6.4.1 User Group Edits - allows a user to add, delete or edit user rights associated with a User Group.

1.6.4.2 User Group Credentials - allows user with appropriate credentials to assign or restrict view and edit functions to groups or individual users. Further management and enrolment of users occurs in the dedicated user page.

Help Text User View Assign: this function allows you to assign controls to restrict viewing and editing of data with project members. You can view a project member's rights and access through the User View function in 'Users'.

1.6.4.3 Remove User from Project: allows an administrator to remove a particular user from a project. The user will have no access to the project and the project will not display in their project menu.

Future Functionality Guest/ Participant Access Admin Page: Function - allows a participants and that meet criteria to be automatically given login passwords and access to a selected fiies or transcripts for participant checking. Such functionality can be expanded to include automated participant contact for warranted events, such as longitudinal projects, contact for final reports and study completion. Function needs to define return email address from database, and select attributes regarding ability to edit documents, track changes and number of logins.

Industry Partner/ De-identification Login: Allows industry partners and researchers to work together in quadrant using identifiable data. Researchers are able to search and select participants based upon non- identifiable data (e.g. choose based upon a purposive sa mple). Once the researchers selects the participants that they wish to enrol in the research, the industry partner receives notirication of the enrolment of selected participants. The Industry partner is then able to contact potential participants to obtain consent to release identifiable information to the researchers {although this is covered in Australia through the NEAF guidelines). This can either be achieved by restricting columns in Data view that correspond to private information or adding additional fields manually once consent has been obtained.

Project File Page

Purpose: The Project Tile Page Is a page which shows all files that are associated with a particular project, workflo and participant. The project file also allows users to export files to other projects or users, and to export files out of the system (e.g. download or email). The project file page also allows for option to show personal, nori project related files. The file page provides ah overview function of a!l files in the system.

Primary Functionalities! View files and sort based upon where they were uploaded to in the system (workflow, participant}. The intent is to allow a user to see a list of transcriptions or sound files. The ability to view and export selected files.

Secondary Functionalities: The ability to add change files to non workflow related files and view file details. Copy files and folders to different projects and to view other file information - date of creation, user creation, Public or private.

Help Text: Workflow files- are files which that belong to a workflow or process. Deleting or modifying a file may affect workflow files stored.

1.7.1 Sort Prefect File Display - Allows users to sort and categorise files that have been entered into the system through workflow entries or attached to participants. Possible a drag and drop unctionality.

1.7.2 Additional Sorts - Displays more complex sort options that users may use - e.g. tags and date of modification, creation or what user created the files.

Notes Page -

Purpose: The Notes page allows users to create and view project wide notes. The notes pages also a'lows the users to export notes out of the system (e.g. download or email), and shows personals, non project related notes. The notes page also provides an overview of al! notes associated with the project including work low and participant notes.

Primary Functionalities: Create and view project specific notes. Secondary Functionalities; View notes and sort based upon where they were added to the system {work low, participant}. The intent is to a liow a user to see a list of notes and to compare across. The ability to view and export selected files. Report Page

Purpose: The report page is designed to al!ow users to develop reports and statistics associated with the participant cohort and completed workflow stages and tasks. Simtlar to saved searches in Dataview reports can be developed sawed and exported. The report page is intended to assist in monitoring the progress of the project and to also assist in developing useful statistics for publishing and dissemination of results. E.g. How many people completed the research? How many people were enrol led but did not complete an interview? What is gender and age of the cohort that completed the qualitative process? Reports are automatically updated.

To assist in simplicity, reports are based on single search criteria and basic natural language presentation of computations. Complex reports can be constructed by adding single line searches together and reorganising them in the Reports list.

Primary Function: To iew arid develop reports associated with the participant cohort and workflow stages and tasks.

Secondary Function: Allow users to select indrvidual reports to display on Project Portal page.

Help Text (General): The reports page allows you to generate reports and analysis to assist you in understanding your patient cohort, purposive sampling and tracking the progress of your project.

Help Text {Combine Unique Values): Combing Unique Values allows you to simplify, group and count similar attributes into the one report, for example, your data may contain entries for Gender as f and Female. Combining these entries will provide a report which sums together these values. To simplify reporting, you can assign a name to these values.

Help Text {Total Patient Cohort): can develop reports which assist in tracking the progress of your project.

Workflow Stage: Select this option is you want to develop reports based upon participant's workflow status.

completed: Select this option if you want to reports and statics concerning participants who have completed all: stages in the workflow. This option is useful if you want to compare characteristics of completed participants to the total cohort or participants that may not have completed all workflow steps.

Example: You con use your reports to mak sure ttiot your sampling corresponas to the overall demographics of your chosen participant cohort.

Total cohort: Select this option f you want to develop reports and statistics based upon all participants that have been imported into Quadrant This option is useful if you want to compare the characteristics of selected participants compared to your entire cohort.

Help Text: Only columns containing values that can be averaged, such as numbers are display in this section. You can only choose one val ue per report line .

Default Reports: To allow users to intuitively understand the reports page, default views should be automatically displayed. Indudtng

1.9.1 Displa in Dashboard - allows user to select a report to appear on their project portal page

1.9.2 Construct Report - allows a user to generate a report based upon a count or average function with Smiting factors according to discrete or unique values and the participant's workflow stage status. Designed to easy and intuitive to use . Natural Language Count Reports

1.9-2.1 Report -CMni jkii participants have completed all workflow stages.

1.9.2.2 Report - Count vo!ite participants are in {Selected) Work km Stage s (Proceed with and for additional selected Workflow Stages).

1.9.2.3 Report -Count i a!ue participants are in the total cohort.

1.9.2.4 Report- Count Votes participants who are (Selected] Unique value have completed all workflow stages.

1.9.2.5 Report - Cot/fit valve participants who are (Selected) Unique value are in (Selected) Workfiov; scsge/s (Proceed with and for addition* selected Workflow Stages). ,

1.9.2.6 Report -Ounr i o ife paftkripants oft e total cohort are unique value

1.9.2.7 Report- Count voias participants who are (Selected) Uniqu ','a'iie (Proceed with and for additional selected Unique vatues).have completed all workflow stages.

1.9.2.8 Report - Count voa'tt participants who are (Selected) unique value (Proceed with and for additional selected unique values) are in (selected) workflow Stoge s (Proceed with and for additional selected Workflow Stages).

1.9.2.9 Report - Count valve participants of the total cohort are Unique value (Proceed with and for additional selected Unique Values)

1.9.2.10 Report- count »-CiV* participants who have attributes listed as first vniqm W«lu* in unique vtrfop list (Proceed with have completed all workflow stages.

1.9.2.11 Report - Co vsiuf participants who are (Selected) First Unique value ip. ur.iafse values list are in Workflow Xn i■ ^■ t {Proceed with and fox additional selected Workflow Stages) .

1.9.2.12 Report - Ctur.t Value participants of the total cohort attributes listed as First nique Value in unm ^' ue 'seioes list

1.9.2.13 Report - oin} si ^' ue participants who are |Selected) user Gene ated Combined valu nsur>e have completed all workflow stages.

1.9.2.14 Report - ccj- "t »*e participants wiho are (Selected) I'str Ge erat combined v¾!u« Name are in Wirtfow lijge s (proceed with and for additional selected Workflow Stages).

1.9.2.15 Report- coy.it value participa nts of the total cohort have attributes listed as (Selected) user eensrsted wb d va'ue usme.

Natural Language Average Reports

1.9.2.16 Report- The average value « cof»uxe Column name el rit ria feft/rsn vtite/ve value participants who have completed all workflow stages is Average Value.

1.9.2.17 Report- The average vo<ue to compute Column iVenrof Criteria cofcw Uniqu Voto* participants who are in «¾>; > .v. stage.- ^' s (Proceed with and for additional selected Workflow Stages) is Average value.

1.9.2.18 Report- The average ctAem Home atwtiaue voiae of the total cohort is Average veto*. 1.9.2.19 Report- The average wtar to Compute Column name of Croatia Column Unique (Proceed with ono* for additional selected Criteria Column Unique Va>1ues|.participants who have completed ail workflow stages is verag value.

1.9.2.20 Report- The average vaMe to Con Utt* Cctu n Name of criteria olumn unique VoSut (Proceed with onrffor additional selected Criteria Column Unique Values) participants who are in Workflow Stage s {Proceed with omf for additional selected Workflow Stages) is Average Vslue.

1.9.2.21 Report- The average Value to Compute Column to/ne of Criteria Column Unique Value (Proceed with and for . additional selected Criteria Column Unique Values) of the total cohort is Average Vot e.

1.9.2.22 Report- The average value to Compute Column Name of user Senenate^ Combiner! Value Name participants who have completed ail workflow stages a Am rage Value.

l.e.2.23 Report - The average value to Compu te column Nam* of urn QtnemteH combined value Hom participants who are in workflow Stsge s (Proceed with and for additional selened Workftow stages) is ή /eray? oiui

LS.2.24 Report - The average vakte to Compute Costimr, Name of crier Ssireratsd Combined value Home of the total cohort ή Average value.

2 Global Notification and System Feedback. (Gf iSF)

Global notification and system feedback broadly refer to system notifications options that should be available to the user through the entire system. They should be recognisable but discrete and enable communication to the user regarding processes and sub- processes that are occurrmg within the system, either from user input or from dient/server processing.

2.1 Screen over Notifica tion

Purpose: To notify users that a action has been taken, but not to inhibit functionality in the main program. - Apparent but discrete. Users should still' have access to page functionalities. Notification can be on top - like GmaiL Screen over notification should also enable to users to reverse action that was Just completed.

Occurs: When a state or function has been changed in Quadrant but does hot originate from a pop up field or query. E.g. Sorting a column from a view from a drop down menu. 'Column has been hidden from view.'

Duration; Notification should last for 3 seconds or until another action has occurred.

2.2 Cursor that spins that signals communication with server

Purpose: To communicate with the user that some process is in progress and that the system is not hanging.

Occurs: When a process is executed, or there is communication between the client and server in which a user cannot continue with other functionality.

Duration: Whilst communication is occurring or process is be ^' ing executed.

2.3. Screen over File Upload Notification Facility

Purpose: To notify users that a file is bemg uploaded and give options for Viewing progress, Cancelling or to upload additional f i!es. Allows users to upload files and access their progress whilst working on other functions of the website.

Occurs: When a user uploads a file or (if possible) through a drag and drop interface.

Duration: Notification remains active until all files have been uploaded. Provides a successful file upload confirmation upon uploading and a link to view file in location. Notification lasts for 3 seconds.

2.4 New element or data added to Dataview Workflow/ Message Highlight

Purpose: To notify users that a new element has been added to the list or moved to a new list (such as a participant) by highlighting the new element.

Occurs: When a user moves or adds a new element (row} into Dataview.

Duration: fs only highlighted until another function is completed on the page.

3 Global Icons and Related Assets (GIRA)

3.1 Select Box

Purpose: For users to select individual or multiple horizontal elements in a list in order for an action to be taken on selected elements.

Occurs: Whenever a list occurs that requires manipulation of more than one element.

Functionality: Toggles selection of elements in a list.

Duration: Whenever a list is present

3.2 Drop Down Menu and Options

Purpose: For users to select additional options that are related to a particular file or task

Occurs: When deemed necessary to hide additional functions that do not have a high frequency of usage.

Functionality: Expands a list to include additional functions.

Duration i Whenever deemed necessary.

3.3 Right Mouse Click

Purpose: For users to instigate or change of function on a particular element of data. Most likely used in Oataview to hide columns, changes states or to delete and update. Most likely, it will house advance functions and features.

Occurs: Whenever there is a list that manipulation can occur on one element of data. Avoids user needing to move mouse to appropriate button.

Functionality: Determined by design.

Duration: Whenever a list is present

3.4 Iconography (Mime)

Purpose: For users to identify different types of files stored in the system.

Occurs: Whenever the system lists an externally up!oaded file or for users choosing to download a file.

Functionality: Mo actuaf functionality apart from conveying file information.

Duration; Whenever an external file is present and is being display.

3.5 Handle to indicate object can be moved.

Purpose: For users to easily identify elements on the website that can be moved or manipulated through dick and drag or mouse inputs. For example, a handle to enable reordering co'umns in the data-view or reordering of files and folders in Project File Page. - Occurs! Whenever elements that ran be manipulated through a drag a drop mechanism.

Functionality: Enables users to grab objects for manipulation..

Duration: Whenever an object displays that can be manipulated through a drag and drop functionality.

3.6 Number of Element Lists display on a page

Purpose: To enable users to choose how information in a list is display according to our a certain criteria. t.g. view elements in a list to display the last 20 chronological entries with a link to display more links or additional ones in a page . E.g. vie first 50 records - display or.

Occurs: Whenever an ongoing list is created and no other sorting elements exist. Most likely in the message window and possible the report menu.

3.7 Field Box Explanatory Text

Purpose: To provide explanatory text in a field without needing to use external elements to describe it.

Functionality: Enables a user to understand what is needed to be entered into a field box . Once user clicks on the field box, the explanatory text disappears.

Occurs: Whenever a field text box may have an ambiguous meaning.

3.Θ Quadrant Progress Indicator and Edit Function

Purpose: As a visual aid and progress indicator. Contains both colour cues and visual cues to indicator progress of a particular workflow or upload. The progress indicator can also be used as a edit control for operations in bulk: data.

Functionality: To enabte a user to quickly judge the progress of a particular function. This could be workflow, file upload or another functton whkh maps progress. The Quadrant Progress indicator should use si ilar colours as the logo or scheme which each colour representing a progress point. A clock type feature should also be incorporated into the design.

Occurs: Whenever there is an option to edit data of a participants workflow or to upload or display some form of communication or progress.

3.9 Default Display of Field Values in Small Display

Purpose: To provide the user with an initiative overview of the participants in which an operation is being carried out but with not presenting aN fields in the database associated with the particular participant. For example : e.g. when manipulating bulk participants in a pop-up. jsuch as J..S.9.1)

Functionality: To enable the user to quickly ascertain participants in which they are about to carry out an operation on (such as change workflow state). E g John Smith. The website should be able to intuitively choose the required fields based upon possibly hierarchy.

De-identified Alias; First; First Name; christian Name; Name; last rtame; Surname or combination of such fields, similarly, the first 2 fields in a Dataview could be displayed

Occurs: Whenever bulk participants are being ma nipulated in a small pop-up and an accurate representation of participant that is being represented.

4 Global Popup Functionality and Data inputs. (GPDI)

Global Popup and Data inputs are pop-ups that enable data input. Every pop up should (where appropriate) be consistently styled and contain elements as below to allow the users to notify other group member, email or export the notifications or files to other users or external parties.

4.1 Privacy - User and Rights Management

Purpose: To enable users to share and edit privacy requirements of the f i'es, notes and appointments as they are uploaded or to previous uploaded files, notes and appointments.

Occurs: Option available in drop down menus or when uploading a file, message or calendar entry. User and rights management generally hidden from view— advanced.

Duration: Only for appointment times in a calendar.

Help Text: Privacy setting can be adjusted so only you or project members you choose have enduring access to the fBe or message. By default everyone who has permissions to view the workflow or participant will have access to the message or file.

4.2 Messages and Notify - Notification and Email Export Functionality

Purpose: Allows for sending message, easy noti ication and export to other users information prevailing to current workflow activities and state changes that a user might complete in normal use of the system. It also allows for personal messages, personal annotation of system (automatic) generated messages and allows for wider dissemination of actions (e.g. send email to external users). The functionality also allows users to notify other users (or themselves) and to export files, notes and calendar entries from the system.

Occurs: Option is to be available on any in send message or notify functionality.

Duration: Lasts as long as file options are presented.

Help Text:

The notify feature assists you in communicating with other project members or external stakeholders any changes or uploads you have instigated with the project.

Piease note:

Depending upon an individual's privacy and user rights:

All changes to projects are automatically included in the Recent Activity tog

Depending upon settings users may outomaticaity receive notification related to changes in workflow and states.

4.3 Assign to - Assign to Functionality

Purpose: Ailows users to assign files or messages to a particular participant or workflow. This functional is automatically enabled if the users inputs data from a participant page (or the workflow page). Users can select fi'e or message to attached through a drop down (or similar) menu item. 4.4 File Upload Popup

Purpose: Allows users to access files and folders to upload to Quadrant.

Occurs: Option is to be available on any input or file function.

Duration: Lasts as long as file options are presented.

4.5 File Upload Progress Popup

Purpose: The file upload progress pop-up is a window that display current file uploads in a pop-up window. It is designed to allow users to view progress whilst working on other aspects in quadrant.

Occurs: When a file is uploaded from either an upload link or a drag and drop functionality.

Functionality: The file upload function enables users to view the upioad and progress of the file upload. They can also cancel file uploads, if more file uploads occur during a current upload. They will be added to the list of file uploads.

Access: File upload progress popup is only assessable once a person chooses to upload a file and then only once they dick the progress indicator button in the Screen Over Notification for file upload.

Duration: The popup is only available whilst a person is uploading files. Close function is available. Pop-up will automatically dose upon completion of all file uploads and provides a notification to the Screen over Notification.

4.6 Help Popup

Purpose: To enable users to access additional information relating to a function or option.

Occurs: When a user accesses the help icon next to functions or other inputs.

Functionality: Allows the user to access information relating to a particular function or option. It is also gives the user the ability to error report or seek operational information from the system administrators.

Access; Popup is only assessable if user selects the fieip notification screen.

Duration: The popup is only available whilst a person selects it. It will disappear when they choose to hide it.

4.7 Ex ort Function

Purpose: To enable user to the export ffes or messages stored with quadrant.

Occurs: When selects the export function.

Functionality: Allows the user to export a fi'e or message or the entire contents of a Quadrant file. User can opt to download text items as a Word, TEXT, PDF or EXCEL file either in individual files or as a combined document. File names or annl.4otations will be displayed as per the object of the text or origin. Individual files (size permitting) will be able to emaiS exported or downloaded as a ZIP file.

Access: Popup is only assessable if user selects the export option.

Duration: The export is only available whilst a person selects it. It ill disappear when they choose to hide it. Help Text: Export allows you to download fiies and messages that are stored within Quadrant. You can download the entire project file through the project administration option.

Please Note:

You will only be able to download information in which your user credentials allow. For greater access contact your Quadrant administrator (send message).

Downloading an entire Quadrant project may take several minutes.

4.8 Details

Purpose: To enable users to access additional information relating to a file upload such as user who generated it, when it was accessed etc.

Occurs: When a user accesses the detail link.

Functionality: Allows a user to view additional or hidden information relating to a particular file or event.

Access: Information is only assessable if user selects the details option.

Duration: The popup is only available whilst a person selects it. It will disappear when they choose to hide it. Help Text:

Details provide you with a view of additional information associated with a file, message or state change.

Quadrant Program Administrator

5.1 Active and archived Projects Overview

5.2 Users Access and Password Management

5.2.1 Customer Reiat ionship Managem ent

5.3 Overall and Project Data Usage Statistics and Access Statistics

5.4 Payment Information and Account Features

Include one oh* payment access, reinstate accounts, free access.

5.5 Scheduled Work (E.g. Transcriptions)

Test Work anding Page

ect Dashboard

LFQ SURVIVORSHIP , ί> X s τ ^'

rch Menu

.1.1 Complex Sort

Add Participant Data

.3.2.1 Add Participant Data

Field Match

Before entering participants - Quadrant will attempt to match columns to existing fields.

Please check that columns represent the intended field.

,3.4 Column Drop Down Menu

1.3.5 More Options

1

1.3.7 Remove All Filters

1.3.8 User View Assign

.3.9 Workflow Operators

3.9.1 Change Participants Workflow Stage

3.9 Assign Participant/s to Workflow

Stages and Tasks

nts

f

V dar

Add/View Appointment

Calender Entry

Location

l*w 1 Jfter 1

Sove Appointment Cancel

Notify ^7 Assign to ^7 Privacy

^■ ^Add View

inistration Page

I

\ / \ 71 \ / \ /

/ \

3

V M

CD

□

□

Project Tools

oject Workflow and Tasks

.1 Assign Workflow

1.6.3.3 Remove User Group

1.6.3.4 Delete Workflow/ Task

ct Users I ^l

I

§7 I

I

1 I 1.6.4.1 User Groups Edits

4.3 Remove User from Project

oject File Page

I j ffl I EB V ¾■ 1.7.1 Sort Project File Display

Sort Project Fife Display

Soff '

1.7.2 Additional

es Page

1.8.1 Notes Page

1.9.1 Display in Dashboard

1.9,2 Construct Report

\

_, _.Ι... v. ._V

2.1 Screen Over Notification

3.1 Select Box

2 Drop Down Menu

Menu Item Not Expanded tens below

1 Privacy

.2 Message and Notify

4.3 Assign

le Upload Notification Facility

Help Pop-Up

Help list

User Selects Help Input

Help Text Display Here

dp 1 Message Displays Wp Message as recorded with function"

4.8 Details

Details

Display Details Relating to File - Latt Modified <reaied ■Created By - Privacy Controls - Cancel