Matt Perhaps I'm missing something here but this is my point - if the components are inter-dependent they both should be updated or none.
? James On 30 September 2010 12:09, <[email protected]> wrote: > I think Kay was quoting my words there : I meant that we need to avoid > (hypothetical) situations where we can't get on and update one component > (where there may be a good reason to do so) because there isn't effort / > resource to update another one that it depends on. A managed approach would > obviously help here, so we don't get caught out. > Matt > > > --------------------------------------------------------- > Please note my working days from 5/1/2009 are Mon, Wed, Thurs only. > [email protected] > > > ------------------------------ > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *James Doughty > *Sent:* 30 September 2010 10:42 > > *To:* NERC DataGrid Technical List > *Cc:* Thomas, David A; Mike Brown > > *Subject:* Re: [ndg-technical] SIS Information Architecture - Business > Processesand People - Configuration Management > > Kay > > New phrase to me is that there 'planning blight'. What do you actually mean > by it? > > In your second paragraph it sounds like the 'Revitalise Data Discovery > Service' project is handling this specifically and as such I will refer to > this in our summary. Clearly it is a very important process and should be > included in the IA Implementation Plan in some shape or form. > > Regards > > James > > On 30 September 2010 09:41, Thorne, Kay <[email protected]> wrote: > >> Hi James/Matt >> >> As Matt mentions: ‘With the "revitalized" service, we've got a new setup >> now, with the backend services (DWS, DPWS) completely separated from the >> front end portal (DDS, DPP). Clearly there's a need to ensure that updates >> to any of these 4 (and the vocab service) are managed together, but also to >> overcome planning blight and ensure that progress can be made with them when >> needed.’ >> >> The back-end services are hosted at CEDA and the front-end portal will be >> hosted at BODC. Consequently, it has already been recognized that the change >> management procedures are an important component of the ‘revitalizing’ >> project. Therefore the project brief contains the deliverable ‘Produce >> protocol document to disseminate procedures and responsibilities for robust >> testing, routine maintenance, trouble shooting, and change management.’ by >> 31/10/2010. It is envisaged that this document will be authored by all >> concerned. >> >> However as Steve Donegan and I undertook the preparation of an important >> (but out of the original ‘revitalizing’ project scope) document to finalize >> NERC Metadata Standard I’ve anticipated that this deliverable will be a >> little behind schedule as work is yet to start. This delay has already be >> communicated to SIB. >> >> Kay >> >> >> >> >> -- >> This message (and any attachments) is for the recipient only. NERC >> is subject to the Freedom of Information Act 2000 and the contents >> of this email and any reply you make may be disclosed by NERC unless >> it is exempt from release under the Act. Any material supplied to >> NERC may be stored in an electronic records management system. >> >> _______________________________________________ >> NDG-technical mailing list >> [email protected] >> http://lists.ncas.ac.uk/mailman/listinfo/ndg-technical >> > > > > -- > James Doughty > Director > Diass Limited > 07985 443973 > [email protected] > > > -- > Scanned by iCritical. > > > _______________________________________________ > NDG-technical mailing list > [email protected] > http://lists.ncas.ac.uk/mailman/listinfo/ndg-technical > -- James Doughty Director Diass Limited 07985 443973 [email protected]
_______________________________________________ NDG-technical mailing list [email protected] http://lists.ncas.ac.uk/mailman/listinfo/ndg-technical
