T1.2 eduGAIN metadata management and attribute release management

Description

Develop, pilot and enhance methods for facilitating attribute release and encouraging take-up by federations, including GÉANT Code of Conduct development and support for R&S within eduGAIN.
Develop and enhance methods for improving metadata management and interoperability, e.g. adoption and customisation of FedLab results.
Develop and enhance methods to ensure quality metadata exchange, e.g. implementation of best practice on metadata streams for eduGAIN.

1.2	eduGAIN Metadata and Attribute Release Management			Devs not available til Sept/Oct, prob not full speed until Jan
	Federation Operational Practice Statement	29/07/2016	Brook
	Check dev implications with Tomasz	Sept
	Outreach for Attribute Release Takeup (CoCo, R&S)	Ongoing		Review after one year
	KPI monitoring & effectiveness monitoring for attribute release	M1 - set up KPI graphs from eduGAIN DB
		M6, M18, M30 effectiveness check		See if this can be automated with Lukas's tools
	Improved audit test/tools (e.g.Fedlab test adoption in eduGAIN)	Y2/Y3		OT will finish integraton of Lukas's tools
	Best practice metadata management - MDS Aggregation Practice Statement [MAPS]	29/07/2016	Brook
	Scalable metadata release tools	Y2, Y3
	Market analysis of developments improving metadata exchange peformance	Y2, Y3
	Monitoring & statistics	M5-M22		Not expllicitly mentioned but needed and can fit in the rubric 'metadata performance'
	Prepare monitoring spec - data required, reports required, import spec, engineering specs	M5
	Prototype with H&S - max 2 federations	M8		Also acts as learning/induction tool for the developers
	Pre-pilot version - inc. partial data from mesh fedederation	M14
	Pilot (provisional) M16-M22	M18-M22
	Attribute translation tools at Federation level - enhance FaaS	Y3
	Update eduGAIN CBA	M8, M20, M32	T0 Brook	Suggest to do this 1x per year rather than for each increment in this subtask unless the investments needed are big

Schedule: every Friday 1-2 pm CEST

none