Message-ID: <171603546.8721.1394232111261.JavaMail.confluence@ece-vmapps> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8720_1762641073.1394232111261" ------=_Part_8720_1762641073.1394232111261 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The only metadata classification we have needed in-house so far is the d= istinction between conceptual and contextual metadata. This probably reflec= ts the fact that we are only just beginning to try to integrate the metadat= a in the production lifecycle.
Here we list the metadata systems per GSBPM phase rather than the metada= ta. Please see section 4 for the contents of our metadata systems.
Specify needs - Vardok, Stabas and Adminstrative system for products, pr= ojects and processes
Design - Stabas and Metadatabase for questionnaires
Build - None
Collect - Datadok, Metadb and Metadatabase for questionnaires
Process - Datadok, Metadb
Analyse - Vardok, Stabas and About the statistics
Disseminate - Metadata portal, About the statistics, About the data coll= ections, StatBank. Service library for metadata systems (Stabas, Vardok, Da= tadok, Metadb).
Our current Adminstrative system for products, projects and processes is= linked to management and budgeting.