Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-Engage:Quality Plan"

From EGIWiki
Jump to navigation Jump to search
Line 4: Line 4:




=== Project management===
= Project management=




=== Document management===
= Document management=
* [[EGI-Engage:Document repository|Document repository]]
==Document repository==
* [[EGI-Engage:Document naming convention|Document naming convention]]
All documents, presentations and other material that forms an official output of the project (not just milestones and deliverables) will be placed in the EGI Document Repository to provide a managed central location for all material.
* [[EGI-Engage:Metadata management|Metadata management]]
 
* [[EGI-Engage:Access to documents|Access to documents]]
 
* [[EGI-Engage:Review process for deliverables and milestones|Review process for deliverables and milestones]]
==Document naming convention==
* [[EGI-Engage:Document management tools|Document management tools]]
*'''Filenames'''
Filenames must use the following format in order to link any item back to other versions placed in the document repository. The filename format is:
 
'''EGI-<DOCUMENT IDENTIFIER>-<REPOSITORY ID>-V<VERSION>'''
 
{| border="1"
|-
| '''DOCUMENT IDENTIFIER''' || The document identifier is dependent on the document type. If the document is:
* Deliverable: Use the deliverable name: e.g. D1.1, D5.5, etc.
* Milestone: Use the milestone name: e.g. MS102, MS504, etc.
* Activity: Use the activity code: e.g. SA1, NA3, etc.
* Committee/Board: Use an acronym based on the committee or board name: e.g. TCB, OMB, UCB, USAG, SPG, etc.
* Other: If the source of the material cannot be identified then ignore this section.||
|-
| '''REPOSITORY ID'''|| This is the identification number generated by the document repository.||
|-
| '''VERSION'''|| This is the version number generated by the document repository for the particular repository identifier.
|-
|}
 
*'''Document titles'''
The title of documents uploaded to document repository must be in the following format:
 
'''<DOCUMENT IDENTIFIER> Title''' (from the first page of the document)
 
Example: [https://documents.egi.eu/public/ShowDocument?docid=60 MS301 User Support Contacts]
 
 
 
==Metadata management==
==Access to documents==
==Review process for deliverables and milestones==
==Document management tools==
* [[EGI-Engage:Copyright|Copyright]]
* [[EGI-Engage:Copyright|Copyright]]
* [http://www.egi.eu/results/glossary/ Glossary]
* [http://www.egi.eu/results/glossary/ Glossary]

Revision as of 17:33, 30 January 2015

EGI-Engage project: Main page WP1(NA1) WP3(JRA1) WP5(SA1) PMB Deliverables and Milestones Quality Plan Risk Plan Data Plan
Roles and
responsibilities
WP2(NA2) WP4(JRA2) WP6(SA2) AMB Software and services Metrics Project Office Procedures





Project management

Document management

Document repository

All documents, presentations and other material that forms an official output of the project (not just milestones and deliverables) will be placed in the EGI Document Repository to provide a managed central location for all material.


Document naming convention

  • Filenames

Filenames must use the following format in order to link any item back to other versions placed in the document repository. The filename format is:

EGI-<DOCUMENT IDENTIFIER>-<REPOSITORY ID>-V<VERSION>

DOCUMENT IDENTIFIER The document identifier is dependent on the document type. If the document is:
  • Deliverable: Use the deliverable name: e.g. D1.1, D5.5, etc.
  • Milestone: Use the milestone name: e.g. MS102, MS504, etc.
  • Activity: Use the activity code: e.g. SA1, NA3, etc.
  • Committee/Board: Use an acronym based on the committee or board name: e.g. TCB, OMB, UCB, USAG, SPG, etc.
  • Other: If the source of the material cannot be identified then ignore this section.||
REPOSITORY ID This is the identification number generated by the document repository.
VERSION This is the version number generated by the document repository for the particular repository identifier.
  • Document titles

The title of documents uploaded to document repository must be in the following format:

<DOCUMENT IDENTIFIER> Title (from the first page of the document)

Example: MS301 User Support Contacts


Metadata management

Access to documents

Review process for deliverables and milestones

Document management tools

Recording project outputs

All output produced by staff active within EGI-InSPIRE (funded and unfunded effort) must be recorded so that it can be reported by the project. The following procedures must be used:

Meetings

The meetings must be recorded in the EGI Indico server and all presentations and material provided for the meeting, including any minutes, must be attached to the appropriate agenda page.

Presentations

Presentations and/or papers presented at other meetings attended by EGI-InSPIRE staff must be recorded in the EGI Document Repository A link to the meeting and a summary of the outcome should be recorded in the ‘notes’ section of the document.

Mailing lists

As the majority of the communication within the project will be electronic having a coherent record of that work is essential. All mailing lists must use the EGI.eu based mailing lists which allow groups defined within the single sign on to be linked to mailing lists, access to wiki space, document access, etc.

Websites

www.egi.eu is the main website for the project. It is used mainly for all ‘official’ ‘static’ content. Individual services supported by EGI.eu will have their own hostname in the egi.eu domain. The wiki has group based access control provided through the EGI SSO system. This can be used for all dynamic content being maintained or developed within each project activity. Other third party websites or wikis should not be used to host EGI-Engage related material in order that the egi.eu domain becomes the definitive source of project information.

Resources