Dataversity & IRIS: Notes from the meeting
Summary
- There are 13 posts — by 5 authors — in this topic.
- Latest post made by Dan Randow at 2010 Mar 05 15:11 NZDT
Good afternoon,
Last Thursday members of Dataversity met with the IRIS Project Director and
an EW Business Analyst to discuss how Dataversity might work with IRIS.
The notes and proposed actions from this meeting are attached.
Questions, comments, suggestions and discussion welcome!
Cheers
Jim
*Dr Jim McLeod*| Regional Data Advocate | Resource Information Group
*Environment Waikato*
P: +64 7 859 0999
M: 021 369 813
E-mail: <email obscured>
PO Box 4010, Hamilton East, Hamilton 3247
++++++++++++++++++++++++++++++++++++++++++
Purpose: To explore how Dataversity might work with IRIS to procure
Biodiversity databases
Meeting Attendees:
Bala Tikkisetty (EW RIG Programme Manager)
Yanbin Deng (EW Biodiversity)
Ryan Clark (EW Biodiversity))
Beat Huser (EW Strategic Projects)
James Lambie (Horizons)
Shay Dean (TRC)
Derek Postlewaight (IRIS Project Director)
Tracey Powrie (EW Business Analyst)
Jim McLeod (EW Regional Data Advocate)
Meeting notes:
1. IRIS presently involves six Regional Councils (RCs) (Northland,
Waikato, Horizons, Taranaki, West Coast and Southland). Discussions are
occurring with two other Regions: Bay of Plenty and Hawkes Bay
2. IRIS core focus is Regional Council; Monitoring (including Consent,
Environmental, Biosecurity, Pest, Selected land use, Incident,
etc), Resource
Consents, Enforcement, Incident Tracking, Central Contacts, Dams, Policy,
Biosecurity, Biodiversity, Customer Service, Land Management, & selected
Land Use. Common core attributes are the contact and spatial aspects.
Details are still being worked on collaboratively by the IRIS Councils.
3. This core application suite and data will interact with others as
appropriate via Webservices. At present the need for direct webservice
access to the IRIS data (cf IRIS applications) has not been raised or
considered.
4. Where appropriate spatial attributes for these data will be
accommodated
5. The preference was to buy a package, but there was nothing suitable.
So IRIS is a development project. In setting the scope for that
development, the preference is not to develop duplicate systems or
services where commercial packages are available. IRIS concentrates on
those requirements RCs have where no commercial product exists. Currently
IRIS 'buy' is for development tools, not applications, each council makes
their own application buy decisions outside of IRIS. For example it is
excepted that each RC will buy its own Finance, Document Management or
Time-series application.
6. Much time has been spent negotiating the Council specific
partnership arrangements
including governance and funding structures.
7. Partners contribute to IRIS funding as a function of six metrics
including the number of staff and number of rate payers, and financial
capacity.
8. Agreement has been for a continuing stream of funding for maintenance and
enhancement of the IRIS application. What happens for new areas of
functionality outside of current scope has not yet been determined.
9. Development Priorities / sequence are still being determined, but
will be agreed by 1 July 2009. The prioritisation process is presently
being developed.
10. Project funding covers Council staff only when they work for the
project office, other than that the project does not cover Council staff
involvement in the project.
11. Communication between IRIS and Councils via a circulation list. One
person in each council has the right to add people to that council's list.
Each council can decide how they circulate the list within that
council. The list will not be filtered based on the requirements of an
individual. If you are on the list because of a specific interest, you get
all the communication, not just your area of interest.
12. The primary target of the IRIS applications are Regional Councils.
Some TAs and Unitary functions are unlikely to be provided by IRIS.
Possible actions for Dataversity members:
1. IRIS engages with the Councils, therefore any involvement of
Dataversity would have to be via those Dataversity members whose Councils
are IRIS partners, and then within the framework of that Council's needs
and agreed IRIS priorities. IRIS will not engage with Dataversity.
Dataversity
could link with IRIS by coordinating the biodiversity needs within the
IRIS Councils and then having those Councils collectively advocate those
needs. (James Lambie to find the Dataversity members who come from IRIS
Councils.)
2. In some Councils, Dataversity has members from biosecurity and from
biodiversity areas. Collaboration between these areas will help achieve
common goals. (Jim McLeod to discuss with Dan Randow about options for
connecting these people.)
3. Dataversity members could collaborate to get TFBIS funding or
Envirolink Funding for biodata in IRIS or funding for a related
initiative to procure a Biodiversity Database/application that
interacts with IRIS via Webservices. (Dataversity IRIS members to
exploreand if appropriate raise with the IRIS Steering Committee
.)
4. To create Biodata specific applications for Councils, Dataversity
might leverage the IRIS governance and funding mechanisms rather than create
a parallel structure within Councils. (Dataversity IRIS members to
explore and if appropriate raise with the IRIS Steering Committee.
5. Communication: Jim McLeod (or an equivalent) should continue to keep the
Dataversity community updated on progress. Dataversity members of the IRIS
Councils need to be active in their Council's IRIS to either ensure that
the biodata aspects are designed in a way that meets their needs or to
identify gaps that need to be filled. Dataversity IRIS members should
also report back together and to the IRIS community on best practice /
tricks of the trade / filling the gaps.
6. Dataversity IRIS members are interested in being able to combining
data from other organisations with IRIS data. For example DOC data.
Attendees to the IRIS meeting were keen to hear how DOC and other central
government agencies were progressing with providing access to their biodata
via Webservices.
**********************************************************************
This email message and any attached files may contain confidential
information, and may be subject to legal professional privilege. If you have
received this message in error, please notify us immediately and destroy the
original message. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of Environment
Waikato. Environment Waikato makes reasonable efforts to ensure that its
email has been scanned and is free of viruses. However, Environment Waikato
can make no warranty that this email or any attachments to it are free from
viruses.
Visit our website at *http://www.ew.govt.nz *
**********************************************************************
Jim, Many thanks for the IRIS update. Could someone explain why IRIS members are not interested in existing biodiversity software: the ARC and EBoP software both have extensible structures that work as (web-linked) biodiversity packages (?).
Regards,
Paul
-----Original Message-----
From: <email obscured>
<email obscured>] On Behalf Of Jim
McLeod
Sent: Wednesday, 8 April 2009 1:55 p.m.
To: <email obscured>
Cc: <email obscured>; <email obscured>;
<email obscured>; <email obscured>;
<email obscured>; <email obscured>
Subject: [dataversity public discussion] Dataversity & IRIS: Notes from
the meeting
Good afternoon,
Last Thursday members of Dataversity met with the IRIS Project Director
and
an EW Business Analyst to discuss how Dataversity might work with IRIS.
The notes and proposed actions from this meeting are attached.
Questions, comments, suggestions and discussion welcome!
Cheers
Jim
*Dr Jim McLeod*| Regional Data Advocate | Resource Information Group
*Environment Waikato*
P: +64 7 859 0999
M: 021 369 813
E-mail: <email obscured>
PO Box 4010, Hamilton East, Hamilton 3247
++++++++++++++++++++++++++++++++++++++++++
Purpose: To explore how Dataversity might work with IRIS to procure
Biodiversity databases
Meeting Attendees:
Bala Tikkisetty (EW RIG Programme Manager)
Yanbin Deng (EW Biodiversity)
Ryan Clark (EW Biodiversity))
Beat Huser (EW Strategic Projects)
James Lambie (Horizons)
Shay Dean (TRC)
Derek Postlewaight (IRIS Project Director)
Tracey Powrie (EW Business Analyst)
Jim McLeod (EW Regional Data Advocate)
Meeting notes:
1. IRIS presently involves six Regional Councils (RCs) (Northland,
Waikato, Horizons, Taranaki, West Coast and Southland). Discussions
are
occurring with two other Regions: Bay of Plenty and Hawkes Bay
2. IRIS core focus is Regional Council; Monitoring (including
Consent,
Environmental, Biosecurity, Pest, Selected land use, Incident,
etc), Resource
Consents, Enforcement, Incident Tracking, Central Contacts, Dams,
Policy,
Biosecurity, Biodiversity, Customer Service, Land Management, &
selected
Land Use. Common core attributes are the contact and spatial
aspects.
Details are still being worked on collaboratively by the IRIS
Councils.
3. This core application suite and data will interact with others as
appropriate via Webservices. At present the need for direct
webservice
access to the IRIS data (cf IRIS applications) has not been raised or
considered.
4. Where appropriate spatial attributes for these data will be
accommodated
5. The preference was to buy a package, but there was nothing
suitable.
So IRIS is a development project. In setting the scope for that
development, the preference is not to develop duplicate systems or
services where commercial packages are available. IRIS concentrates
on
those requirements RCs have where no commercial product exists.
Currently
IRIS 'buy' is for development tools, not applications, each council
makes
their own application buy decisions outside of IRIS. For example it
is
excepted that each RC will buy its own Finance, Document Management
or
Time-series application.
6. Much time has been spent negotiating the Council specific
partnership arrangements
including governance and funding structures.
7. Partners contribute to IRIS funding as a function of six metrics
including the number of staff and number of rate payers, and
financial
capacity.
8. Agreement has been for a continuing stream of funding for
maintenance and
enhancement of the IRIS application. What happens for new areas of
functionality outside of current scope has not yet been determined.
9. Development Priorities / sequence are still being determined, but
will be agreed by 1 July 2009. The prioritisation process is
presently
being developed.
10. Project funding covers Council staff only when they work for the
project office, other than that the project does not cover Council
staff
involvement in the project.
11. Communication between IRIS and Councils via a circulation list.
One
person in each council has the right to add people to that council's
list.
Each council can decide how they circulate the list within that
council. The list will not be filtered based on the requirements of
an
individual. If you are on the list because of a specific interest,
you get
all the communication, not just your area of interest.
12. The primary target of the IRIS applications are Regional
Councils.
Some TAs and Unitary functions are unlikely to be provided by IRIS.
Possible actions for Dataversity members:
1. IRIS engages with the Councils, therefore any involvement of
Dataversity would have to be via those Dataversity members whose
Councils
are IRIS partners, and then within the framework of that Council's
needs
and agreed IRIS priorities. IRIS will not engage with Dataversity.
Dataversity
could link with IRIS by coordinating the biodiversity needs within
the
IRIS Councils and then having those Councils collectively advocate
those
needs. (James Lambie to find the Dataversity members who come from
IRIS
Councils.)
2. In some Councils, Dataversity has members from biosecurity and
from
biodiversity areas. Collaboration between these areas will help
achieve
common goals. (Jim McLeod to discuss with Dan Randow about options
for
connecting these people.)
3. Dataversity members could collaborate to get TFBIS funding or
Envirolink Funding for biodata in IRIS or funding for a related
initiative to procure a Biodiversity Database/application that
interacts with IRIS via Webservices. (Dataversity IRIS members to
exploreand if appropriate raise with the IRIS Steering Committee
.)
4. To create Biodata specific applications for Councils, Dataversity
might leverage the IRIS governance and funding mechanisms rather than
create
a parallel structure within Councils. (Dataversity IRIS members to
explore and if appropriate raise with the IRIS Steering Committee.
5. Communication: Jim McLeod (or an equivalent) should continue to
keep the
Dataversity community updated on progress. Dataversity members of
the IRIS
Councils need to be active in their Council's IRIS to either ensure
that
the biodata aspects are designed in a way that meets their needs or
to
identify gaps that need to be filled. Dataversity IRIS members
should
also report back together and to the IRIS community on best practice
/
tricks of the trade / filling the gaps.
6. Dataversity IRIS members are interested in being able to combining
data from other organisations with IRIS data. For example DOC data.
Attendees to the IRIS meeting were keen to hear how DOC and other
central
government agencies were progressing with providing access to their
biodata
via Webservices.
**********************************************************************
This email message and any attached files may contain confidential
information, and may be subject to legal professional privilege. If you
have
received this message in error, please notify us immediately and destroy
the
original message. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of
Environment
Waikato. Environment Waikato makes reasonable efforts to ensure that its
email has been scanned and is free of viruses. However, Environment
Waikato
can make no warranty that this email or any attachments to it are free
from
viruses.
Visit our website at *http://www.ew.govt.nz *
**********************************************************************
-----------------------------------------
Full text of this topic in Dataversity Public Discussion:
http://dataversity.org.nz/r/topic/7wMoHSciexaGSsY9R6Qlr6
To leave Dataversity Public Discussion, email
<email obscured>?Subject=unsubscribe
Start your own free groups and site with
OnlineGroups.Net http://onlinegroups.net
You are prohibited from distributing this E-mail without permission. If you
have received this E-mail by mistake or are not the intended recipient, please
notify the sender and erase the message immediately. This E-mail message and
any accompanying data is confidential and may be legally privileged. The Nelson
City Council does not warrant or guarantee that this communication is free of
errors, virus or interference.
This e-mail has been scanned and cleared by MailMarshal.
I believe the answer here is that they haven't yet got together the biodata requirements of the IRIS councils, therefore they haven't made a decision on whether or not the ARC / EBOP software fits those requirements.What they are presently (or will shortly be) doing is the prioritisation of functional areas then looking at the needs of those areas. Shay, Jim Lambie - comments?
On Wed, Apr 8, 2009 at 2:37 PM, Paul Fisher <email obscured>> wrote: > Jim, > > Many thanks for the IRIS update. Could someone explain why IRIS members > are not interested in existing biodiversity software: the ARC and EBoP > software both have extensible structures that work as (web-linked) > biodiversity packages (?). > > Regards, > Paul > > -----Original Message----- > From: <email obscured> > <email obscured>] On Behalf Of Jim > McLeod > Sent: Wednesday, 8 April 2009 1:55 p.m. > To: <email obscured> > Cc: <email obscured>; <email obscured>; > <email obscured>; <email obscured>; > <email obscured>; <email obscured> > Subject: [dataversity public discussion] Dataversity & IRIS: Notes from > the meeting > > Good afternoon, > > Last Thursday members of Dataversity met with the IRIS Project Director > and > an EW Business Analyst to discuss how Dataversity might work with IRIS. > > The notes and proposed actions from this meeting are attached. > > Questions, comments, suggestions and discussion welcome! > > Cheers > Jim > > > *Dr Jim McLeod*| Regional Data Advocate | Resource Information Group > *Environment Waikato* > P: +64 7 859 0999 > M: 021 369 813 > E-mail: <email obscured> > PO Box 4010, Hamilton East, Hamilton 3247 > > ++++++++++++++++++++++++++++++++++++++++++ > Purpose: To explore how Dataversity might work with IRIS to procure > Biodiversity databases > > Meeting Attendees: > > Bala Tikkisetty (EW RIG Programme Manager) > Yanbin Deng (EW Biodiversity) > Ryan Clark (EW Biodiversity)) > Beat Huser (EW Strategic Projects) > James Lambie (Horizons) > Shay Dean (TRC) > Derek Postlewaight (IRIS Project Director) > Tracey Powrie (EW Business Analyst) > Jim McLeod (EW Regional Data Advocate) > > Meeting notes: > > 1. IRIS presently involves six Regional Councils (RCs) (Northland, > Waikato, Horizons, Taranaki, West Coast and Southland). Discussions > are > occurring with two other Regions: Bay of Plenty and Hawkes Bay > 2. IRIS core focus is Regional Council; Monitoring (including > Consent, > Environmental, Biosecurity, Pest, Selected land use, Incident, > etc), Resource > Consents, Enforcement, Incident Tracking, Central Contacts, Dams, > Policy, > Biosecurity, Biodiversity, Customer Service, Land Management, & > selected > Land Use. Common core attributes are the contact and spatial > aspects. > Details are still being worked on collaboratively by the IRIS > Councils. > 3. This core application suite and data will interact with others as > appropriate via Webservices. At present the need for direct > webservice > access to the IRIS data (cf IRIS applications) has not been raised or > considered. > 4. Where appropriate spatial attributes for these data will be > accommodated > 5. The preference was to buy a package, but there was nothing > suitable. > So IRIS is a development project. In setting the scope for that > development, the preference is not to develop duplicate systems or > services where commercial packages are available. IRIS concentrates > on > those requirements RCs have where no commercial product exists. > Currently > IRIS 'buy' is for development tools, not applications, each council > makes > their own application buy decisions outside of IRIS. For example it > is > excepted that each RC will buy its own Finance, Document Management > or > Time-series application. > 6. Much time has been spent negotiating the Council specific > partnership arrangements > including governance and funding structures. > 7. Partners contribute to IRIS funding as a function of six metrics > including the number of staff and number of rate payers, and > financial > capacity. > 8. Agreement has been for a continuing stream of funding for > maintenance and > enhancement of the IRIS application. What happens for new areas of > functionality outside of current scope has not yet been determined. > 9. Development Priorities / sequence are still being determined, but > will be agreed by 1 July 2009. The prioritisation process is > presently > being developed. > 10. Project funding covers Council staff only when they work for the > project office, other than that the project does not cover Council > staff > involvement in the project. > 11. Communication between IRIS and Councils via a circulation list. > One > person in each council has the right to add people to that council's > list. > Each council can decide how they circulate the list within that > council. The list will not be filtered based on the requirements of > an > individual. If you are on the list because of a specific interest, > you get > all the communication, not just your area of interest. > 12. The primary target of the IRIS applications are Regional > Councils. > Some TAs and Unitary functions are unlikely to be provided by IRIS. > > Possible actions for Dataversity members: > > 1. IRIS engages with the Councils, therefore any involvement of > Dataversity would have to be via those Dataversity members whose > Councils > are IRIS partners, and then within the framework of that Council's > needs > and agreed IRIS priorities. IRIS will not engage with Dataversity. > Dataversity > could link with IRIS by coordinating the biodiversity needs within > the > IRIS Councils and then having those Councils collectively advocate > those > needs. (James Lambie to find the Dataversity members who come from > IRIS > Councils.) > 2. In some Councils, Dataversity has members from biosecurity and > from > biodiversity areas. Collaboration between these areas will help > achieve > common goals. (Jim McLeod to discuss with Dan Randow about options > for > connecting these people.) > 3. Dataversity members could collaborate to get TFBIS funding or > Envirolink Funding for biodata in IRIS or funding for a related > initiative to procure a Biodiversity Database/application that > interacts with IRIS via Webservices. (Dataversity IRIS members to > exploreand if appropriate raise with the IRIS Steering Committee > .) > 4. To create Biodata specific applications for Councils, Dataversity > might leverage the IRIS governance and funding mechanisms rather than > create > a parallel structure within Councils. (Dataversity IRIS members to > explore and if appropriate raise with the IRIS Steering Committee. > 5. Communication: Jim McLeod (or an equivalent) should continue to > keep the > Dataversity community updated on progress. Dataversity members of > the IRIS > Councils need to be active in their Council's IRIS to either ensure > that > the biodata aspects are designed in a way that meets their needs or > to > identify gaps that need to be filled. Dataversity IRIS members > should > also report back together and to the IRIS community on best practice > / > tricks of the trade / filling the gaps. > 6. Dataversity IRIS members are interested in being able to combining > data from other organisations with IRIS data. For example DOC data. > Attendees to the IRIS meeting were keen to hear how DOC and other > central > government agencies were progressing with providing access to their > biodata > via Webservices. > > > > > ********************************************************************** > > This email message and any attached files may contain confidential > information, and may be subject to legal professional privilege. If you > have > received this message in error, please notify us immediately and destroy > the > original message. Any views expressed in this message are those of the > individual sender and may not necessarily reflect the views of > Environment > Waikato. Environment Waikato makes reasonable efforts to ensure that its > email has been scanned and is free of viruses. However, Environment > Waikato > can make no warranty that this email or any attachments to it are free > from > viruses. > > Visit our website at *http://www.ew.govt.nz * > > ********************************************************************** > > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/7wMoHSciexaGSsY9R6Qlr6 > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscribe > > Start your own free groups and site with > OnlineGroups.Net http://onlinegroups.net > You are prohibited from distributing this E-mail without permission. If you > have received this E-mail by mistake or are not the intended recipient, > please notify the sender and erase the message immediately. This E-mail > message and any accompanying data is confidential and may be legally > privileged. The Nelson City Council does not warrant or guarantee that this > communication is free of errors, virus or interference. > > This e-mail has been scanned and cleared by MailMarshal. > > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/3roMVZnebCjQnSbtBS2mi5 > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscribe > > Start your own free groups and site with > OnlineGroups.Net http://onlinegroups.net >
Thanks Jim
-----Original Message----- From: <email obscured> <email obscured>] On Behalf Of Jim McLeod Sent: Wednesday, 8 April 2009 3:15 p.m. To: <email obscured> Subject: Re: [dataversity public discussion] Dataversity & IRIS: Notes from the meeting I believe the answer here is that they haven't yet got together the biodata requirements of the IRIS councils, therefore they haven't made a decision on whether or not the ARC / EBOP software fits those requirements.What they are presently (or will shortly be) doing is the prioritisation of functional areas then looking at the needs of those areas. Shay, Jim Lambie - comments? On Wed, Apr 8, 2009 at 2:37 PM, Paul Fisher <email obscured>> wrote: > Jim, > > Many thanks for the IRIS update. Could someone explain why IRIS members > are not interested in existing biodiversity software: the ARC and EBoP > software both have extensible structures that work as (web-linked) > biodiversity packages (?). > > Regards, > Paul > > -----Original Message----- > From: <email obscured> > <email obscured>] On Behalf Of Jim > McLeod > Sent: Wednesday, 8 April 2009 1:55 p.m. > To: <email obscured> > Cc: <email obscured>; <email obscured>; > <email obscured>; <email obscured>; > <email obscured>; <email obscured> > Subject: [dataversity public discussion] Dataversity & IRIS: Notes from > the meeting > > Good afternoon, > > Last Thursday members of Dataversity met with the IRIS Project Director > and > an EW Business Analyst to discuss how Dataversity might work with IRIS. > > The notes and proposed actions from this meeting are attached. > > Questions, comments, suggestions and discussion welcome! > > Cheers > Jim > > > *Dr Jim McLeod*| Regional Data Advocate | Resource Information Group > *Environment Waikato* > P: +64 7 859 0999 > M: 021 369 813 > E-mail: <email obscured> > PO Box 4010, Hamilton East, Hamilton 3247 > > ++++++++++++++++++++++++++++++++++++++++++ > Purpose: To explore how Dataversity might work with IRIS to procure > Biodiversity databases > > Meeting Attendees: > > Bala Tikkisetty (EW RIG Programme Manager) > Yanbin Deng (EW Biodiversity) > Ryan Clark (EW Biodiversity)) > Beat Huser (EW Strategic Projects) > James Lambie (Horizons) > Shay Dean (TRC) > Derek Postlewaight (IRIS Project Director) > Tracey Powrie (EW Business Analyst) > Jim McLeod (EW Regional Data Advocate) > > Meeting notes: > > 1. IRIS presently involves six Regional Councils (RCs) (Northland, > Waikato, Horizons, Taranaki, West Coast and Southland). Discussions > are > occurring with two other Regions: Bay of Plenty and Hawkes Bay > 2. IRIS core focus is Regional Council; Monitoring (including > Consent, > Environmental, Biosecurity, Pest, Selected land use, Incident, > etc), Resource > Consents, Enforcement, Incident Tracking, Central Contacts, Dams, > Policy, > Biosecurity, Biodiversity, Customer Service, Land Management, & > selected > Land Use. Common core attributes are the contact and spatial > aspects. > Details are still being worked on collaboratively by the IRIS > Councils. > 3. This core application suite and data will interact with others as > appropriate via Webservices. At present the need for direct > webservice > access to the IRIS data (cf IRIS applications) has not been raised or > considered. > 4. Where appropriate spatial attributes for these data will be > accommodated > 5. The preference was to buy a package, but there was nothing > suitable. > So IRIS is a development project. In setting the scope for that > development, the preference is not to develop duplicate systems or > services where commercial packages are available. IRIS concentrates > on > those requirements RCs have where no commercial product exists. > Currently > IRIS 'buy' is for development tools, not applications, each council > makes > their own application buy decisions outside of IRIS. For example it > is > excepted that each RC will buy its own Finance, Document Management > or > Time-series application. > 6. Much time has been spent negotiating the Council specific > partnership arrangements > including governance and funding structures. > 7. Partners contribute to IRIS funding as a function of six metrics > including the number of staff and number of rate payers, and > financial > capacity. > 8. Agreement has been for a continuing stream of funding for > maintenance and > enhancement of the IRIS application. What happens for new areas of > functionality outside of current scope has not yet been determined. > 9. Development Priorities / sequence are still being determined, but > will be agreed by 1 July 2009. The prioritisation process is > presently > being developed. > 10. Project funding covers Council staff only when they work for the > project office, other than that the project does not cover Council > staff > involvement in the project. > 11. Communication between IRIS and Councils via a circulation list. > One > person in each council has the right to add people to that council's > list. > Each council can decide how they circulate the list within that > council. The list will not be filtered based on the requirements of > an > individual. If you are on the list because of a specific interest, > you get > all the communication, not just your area of interest. > 12. The primary target of the IRIS applications are Regional > Councils. > Some TAs and Unitary functions are unlikely to be provided by IRIS. > > Possible actions for Dataversity members: > > 1. IRIS engages with the Councils, therefore any involvement of > Dataversity would have to be via those Dataversity members whose > Councils > are IRIS partners, and then within the framework of that Council's > needs > and agreed IRIS priorities. IRIS will not engage with Dataversity. > Dataversity > could link with IRIS by coordinating the biodiversity needs within > the > IRIS Councils and then having those Councils collectively advocate > those > needs. (James Lambie to find the Dataversity members who come from > IRIS > Councils.) > 2. In some Councils, Dataversity has members from biosecurity and > from > biodiversity areas. Collaboration between these areas will help > achieve > common goals. (Jim McLeod to discuss with Dan Randow about options > for > connecting these people.) > 3. Dataversity members could collaborate to get TFBIS funding or > Envirolink Funding for biodata in IRIS or funding for a related > initiative to procure a Biodiversity Database/application that > interacts with IRIS via Webservices. (Dataversity IRIS members to > exploreand if appropriate raise with the IRIS Steering Committee > .) > 4. To create Biodata specific applications for Councils, Dataversity > might leverage the IRIS governance and funding mechanisms rather than > create > a parallel structure within Councils. (Dataversity IRIS members to > explore and if appropriate raise with the IRIS Steering Committee. > 5. Communication: Jim McLeod (or an equivalent) should continue to > keep the > Dataversity community updated on progress. Dataversity members of > the IRIS > Councils need to be active in their Council's IRIS to either ensure > that > the biodata aspects are designed in a way that meets their needs or > to > identify gaps that need to be filled. Dataversity IRIS members > should > also report back together and to the IRIS community on best practice > / > tricks of the trade / filling the gaps. > 6. Dataversity IRIS members are interested in being able to combining > data from other organisations with IRIS data. For example DOC data. > Attendees to the IRIS meeting were keen to hear how DOC and other > central > government agencies were progressing with providing access to their > biodata > via Webservices. > > > > > ********************************************************************** > > This email message and any attached files may contain confidential > information, and may be subject to legal professional privilege. If you > have > received this message in error, please notify us immediately and destroy > the > original message. Any views expressed in this message are those of the > individual sender and may not necessarily reflect the views of > Environment > Waikato. Environment Waikato makes reasonable efforts to ensure that its > email has been scanned and is free of viruses. However, Environment > Waikato > can make no warranty that this email or any attachments to it are free > from > viruses. > > Visit our website at *http://www.ew.govt.nz * > > ********************************************************************** > > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/7wMoHSciexaGSsY9R6Qlr6 > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscribe > > Start your own free groups and site with > OnlineGroups.Net http://onlinegroups.net > You are prohibited from distributing this E-mail without permission. If you > have received this E-mail by mistake or are not the intended recipient, > please notify the sender and erase the message immediately. This E-mail > message and any accompanying data is confidential and may be legally > privileged. The Nelson City Council does not warrant or guarantee that this > communication is free of errors, virus or interference. > > This e-mail has been scanned and cleared by MailMarshal. > > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/3roMVZnebCjQnSbtBS2mi5 > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscribe > > Start your own free groups and site with > OnlineGroups.Net http://onlinegroups.net > ----------------------------------------- Full text of this topic in Dataversity Public Discussion: http://dataversity.org.nz/r/topic/TfAn3Z5qV0Qy1ik6JYIn3 To leave Dataversity Public Discussion, email <email obscured>?Subject=unsubscribe Start your own free groups and site with OnlineGroups.Net http://onlinegroups.net You are prohibited from distributing this E-mail without permission. If you have received this E-mail by mistake or are not the intended recipient, please notify the sender and erase the message immediately. This E-mail message and any accompanying data is confidential and may be legally privileged. The Nelson City Council does not warrant or guarantee that this communication is free of errors, virus or interference. This e-mail has been scanned and cleared by MailMarshal.
Sounds right to me - I only became aware of the IRIS project just before the Wellington meeting and there has not been any chance yet to sit down and work out what fits.
-----Original Message----- From: <email obscured> <email obscured>] On Behalf Of Jim McLeod Sent: Wednesday, 8 April 2009 3:15 p.m. To: <email obscured> Subject: Re: [dataversity public discussion] Dataversity & IRIS: Notes from the meeting I believe the answer here is that they haven't yet got together the biodata requirements of the IRIS councils, therefore they haven't made a decision on whether or not the ARC / EBOP software fits those requirements.What they are presently (or will shortly be) doing is the prioritisation of functional areas then looking at the needs of those areas. Shay, Jim Lambie - comments? On Wed, Apr 8, 2009 at 2:37 PM, Paul Fisher <email obscured>> wrote: > Jim, > > Many thanks for the IRIS update. Could someone explain why IRIS > members are not interested in existing biodiversity software: the ARC > and EBoP software both have extensible structures that work as > (web-linked) biodiversity packages (?). > > Regards, > Paul > > -----Original Message----- > From: <email obscured> > <email obscured>] On Behalf Of > Jim McLeod > Sent: Wednesday, 8 April 2009 1:55 p.m. > To: <email obscured> > Cc: <email obscured>; <email obscured>; > <email obscured>; <email obscured>; > <email obscured>; <email obscured> > Subject: [dataversity public discussion] Dataversity & IRIS: Notes > from the meeting > > Good afternoon, > > Last Thursday members of Dataversity met with the IRIS Project > Director and an EW Business Analyst to discuss how Dataversity might > work with IRIS. > > The notes and proposed actions from this meeting are attached. > > Questions, comments, suggestions and discussion welcome! > > Cheers > Jim > > > *Dr Jim McLeod*| Regional Data Advocate | Resource Information Group > *Environment Waikato* > P: +64 7 859 0999 > M: 021 369 813 > E-mail: <email obscured> > PO Box 4010, Hamilton East, Hamilton 3247 > > ++++++++++++++++++++++++++++++++++++++++++ > Purpose: To explore how Dataversity might work with IRIS to procure > Biodiversity databases > > Meeting Attendees: > > Bala Tikkisetty (EW RIG Programme Manager) Yanbin Deng (EW > Biodiversity) Ryan Clark (EW Biodiversity)) Beat Huser (EW Strategic > Projects) James Lambie (Horizons) Shay Dean (TRC) Derek Postlewaight > (IRIS Project Director) Tracey Powrie (EW Business Analyst) Jim McLeod > (EW Regional Data Advocate) > > Meeting notes: > > 1. IRIS presently involves six Regional Councils (RCs) (Northland, > Waikato, Horizons, Taranaki, West Coast and Southland). Discussions > are > occurring with two other Regions: Bay of Plenty and Hawkes Bay > 2. IRIS core focus is Regional Council; Monitoring (including > Consent, > Environmental, Biosecurity, Pest, Selected land use, Incident, etc), > Resource > Consents, Enforcement, Incident Tracking, Central Contacts, Dams, > Policy, > Biosecurity, Biodiversity, Customer Service, Land Management, & > selected > Land Use. Common core attributes are the contact and spatial > aspects. > Details are still being worked on collaboratively by the IRIS > Councils. > 3. This core application suite and data will interact with others as > appropriate via Webservices. At present the need for direct > webservice > access to the IRIS data (cf IRIS applications) has not been raised or > considered. > 4. Where appropriate spatial attributes for these data will be > accommodated > 5. The preference was to buy a package, but there was nothing > suitable. > So IRIS is a development project. In setting the scope for that > development, the preference is not to develop duplicate systems or > services where commercial packages are available. IRIS concentrates > on > those requirements RCs have where no commercial product exists. > Currently > IRIS 'buy' is for development tools, not applications, each council > makes > their own application buy decisions outside of IRIS. For example it > is > excepted that each RC will buy its own Finance, Document Management > or > Time-series application. > 6. Much time has been spent negotiating the Council specific > partnership arrangements > including governance and funding structures. > 7. Partners contribute to IRIS funding as a function of six metrics > including the number of staff and number of rate payers, and > financial > capacity. > 8. Agreement has been for a continuing stream of funding for > maintenance and > enhancement of the IRIS application. What happens for new areas of > functionality outside of current scope has not yet been determined. > 9. Development Priorities / sequence are still being determined, but > will be agreed by 1 July 2009. The prioritisation process is > presently > being developed. > 10. Project funding covers Council staff only when they work for the > project office, other than that the project does not cover Council > staff > involvement in the project. > 11. Communication between IRIS and Councils via a circulation list. > One > person in each council has the right to add people to that council's > list. > Each council can decide how they circulate the list within that > council. The list will not be filtered based on the requirements of > an > individual. If you are on the list because of a specific interest, > you get > all the communication, not just your area of interest. > 12. The primary target of the IRIS applications are Regional > Councils. > Some TAs and Unitary functions are unlikely to be provided by IRIS. > > Possible actions for Dataversity members: > > 1. IRIS engages with the Councils, therefore any involvement of > Dataversity would have to be via those Dataversity members whose > Councils > are IRIS partners, and then within the framework of that Council's > needs > and agreed IRIS priorities. IRIS will not engage with Dataversity. > Dataversity > could link with IRIS by coordinating the biodiversity needs within > the > IRIS Councils and then having those Councils collectively advocate > those > needs. (James Lambie to find the Dataversity members who come from > IRIS > Councils.) > 2. In some Councils, Dataversity has members from biosecurity and > from > biodiversity areas. Collaboration between these areas will help > achieve > common goals. (Jim McLeod to discuss with Dan Randow about options > for > connecting these people.) > 3. Dataversity members could collaborate to get TFBIS funding or > Envirolink Funding for biodata in IRIS or funding for a related > initiative to procure a Biodiversity Database/application that > interacts with IRIS via Webservices. (Dataversity IRIS members to > exploreand if appropriate raise with the IRIS Steering Committee > .) > 4. To create Biodata specific applications for Councils, Dataversity > might leverage the IRIS governance and funding mechanisms rather > than create > a parallel structure within Councils. (Dataversity IRIS members to > explore and if appropriate raise with the IRIS Steering Committee. > 5. Communication: Jim McLeod (or an equivalent) should continue to > keep the > Dataversity community updated on progress. Dataversity members of > the IRIS > Councils need to be active in their Council's IRIS to either ensure > that > the biodata aspects are designed in a way that meets their needs or > to > identify gaps that need to be filled. Dataversity IRIS members > should > also report back together and to the IRIS community on best practice > / > tricks of the trade / filling the gaps. > 6. Dataversity IRIS members are interested in being able to combining > data from other organisations with IRIS data. For example DOC data. > Attendees to the IRIS meeting were keen to hear how DOC and other > central > government agencies were progressing with providing access to their > biodata > via Webservices. > > > > > ********************************************************************** > > This email message and any attached files may contain confidential > information, and may be subject to legal professional privilege. If > you have received this message in error, please notify us immediately > and destroy the original message. Any views expressed in this message > are those of the individual sender and may not necessarily reflect the > views of Environment Waikato. Environment Waikato makes reasonable > efforts to ensure that its email has been scanned and is free of > viruses. However, Environment Waikato can make no warranty that this > email or any attachments to it are free from viruses. > > Visit our website at *http://www.ew.govt.nz * > > ********************************************************************** > > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/7wMoHSciexaGSsY9R6Qlr6 > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscri > be > > Start your own free groups and site with OnlineGroups.Net > http://onlinegroups.net You are prohibited from distributing this > E-mail without permission. If you have received this E-mail by mistake > or are not the intended recipient, please notify the sender and erase > the message immediately. This E-mail message and any accompanying > data is confidential and may be legally privileged. The Nelson City > Council does not warrant or guarantee that this communication is free > of errors, virus or interference. > > This e-mail has been scanned and cleared by MailMarshal. > > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/3roMVZnebCjQnSbtBS2mi5 > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscri > be > > Start your own free groups and site with OnlineGroups.Net > http://onlinegroups.net > ----------------------------------------- Full text of this topic in Dataversity Public Discussion: http://dataversity.org.nz/r/topic/TfAn3Z5qV0Qy1ik6JYIn3 To leave Dataversity Public Discussion, email <email obscured>?Subject=unsubscribe Start your own free groups and site with OnlineGroups.Net http://onlinegroups.net Horizons Regional Council | 24 hr freephone 0508 800 800 | www.horizons.govt.nz This email is covered by the disclaimers which can be found here: http://www.horizons.govt.nz/default.aspx?pageid=219
Many thanks for that report, Jim,
> 1. IRIS presently involves six Regional Councils (RCs) (Northland,
> Waikato, Horizons, Taranaki, West Coast and Southland). Discussions are
> occurring with two other Regions: Bay of Plenty and Hawkes Bay
We have good representation from some of these in Dataversity.
Environment Bay of Plenty
Heather MacKenzie
Jim Fretwell
Environment Waikato
Yanbin Deng
Ryan Clark
Derek Phyn
Jim McLeod
Horizons Regional Council
James Lambie
Northland Regional Council
Wayne Teal
Kathy Mortimer
Lisa Forester
Taranaki Regional Council
Shay Dean
For others, we do not have good representation.
West Coast Regional Council
Environment Southland
Hawke's Bay Regional Council
I'll work on these.
> 11. Communication between IRIS and Councils via a circulation list. One
> person in each council has the right to add people to that council's list.
> Each council can decide how they circulate the list within that
> council.
Based on this, then Dataversity members interested in IRIS should
identify that person in their own Council, and ask to be on the
circulation list.
> 1. IRIS engages with the Councils, therefore any involvement of
> Dataversity would have to be via those Dataversity members whose Councils
> are IRIS partners, and then within the framework of that Council's needs
> and agreed IRIS priorities. IRIS will not engage with Dataversity.
> Dataversity
> could link with IRIS by coordinating the biodiversity needs within the
> IRIS Councils and then having those Councils collectively advocate those
> needs.
OK, so if Dataversity members agree a shared message, and send that back
consistently through their own council, there is a chance it will reach
IRIS.
> (James Lambie to find the Dataversity members who come from IRIS
> Councils.)
Jim, the above list should help with this. Happy to help you further
with this.
> 2. In some Councils, Dataversity has members from biosecurity and from
> biodiversity areas. Collaboration between these areas will help achieve
> common goals. (Jim McLeod to discuss with Dan Randow about options for
> connecting these people.)
Dan Randow is already widening the Dataversity membership to include
more biosecurity people, and planning more formal links with the BMG.
> 3. Dataversity members could collaborate to get TFBIS funding or
> Envirolink Funding for biodata in IRIS or funding for a related
> initiative to procure a Biodiversity Database/application that
> interacts with IRIS via Webservices. (Dataversity IRIS members to
> exploreand if appropriate raise with the IRIS Steering Committee
> .)
> 4. To create Biodata specific applications for Councils, Dataversity
> might leverage the IRIS governance and funding mechanisms rather than
create
> a parallel structure within Councils. (Dataversity IRIS members to
> explore and if appropriate raise with the IRIS Steering Committee.
I think it is still early days to be thinking about procurement,
especially if that actually means development. There are many decisions
about standards and protocols to be made, and many existing systems to
be evaluated first. Although this may be worth pursuing, would it not
also make sense to at least agree some requirements about the types of
data handling and services that are required from IRIS? If this could be
achieved, then there is a chance that IRIS will be able to share data
with a variety of biodata applications, as long as they are talking more
or less the standard language? See Opportunity "3.4 Agree and Adopt
National Shared Standards" from the National Workshop Report.
http://dataversity.org.nz/r/file/3153-2009-04-07T074110Z/Dataversity%20National%20Workshop%20Report.pdf
As IRIS is at the requirements prioritisation stage, would it be better
to go for "share data with standards-compliant biodata systems" or "be
our ultimate biodata system"?
> 5. Communication: Jim McLeod (or an equivalent) should continue to keep
the
> Dataversity community updated on progress. Dataversity members of the
IRIS
> Councils need to be active in their Council's IRIS to either ensure that
> the biodata aspects are designed in a way that meets their needs or to
> identify gaps that need to be filled. Dataversity IRIS members should
> also report back together and to the IRIS community on best practice /
> tricks of the trade / filling the gaps.
Agreed.
> 6. Dataversity IRIS members are interested in being able to combining
> data from other organisations with IRIS data. For example DOC data.
> Attendees to the IRIS meeting were keen to hear how DOC and other central
> government agencies were progressing with providing access to their
biodata
> via Webservices.
Yes, the above requirement "share data with standards-compliant biodata
systems" might provide the local government end of this, out of the box.
Dan
This sounds right to me too, engaging IRIS does not mean we are not interested in ARC and EBOPs software. IRIS will assess the ability of ARC and EBOPs software to meet our requirements for us and will not be duplicating software that is available "off the shelf". Shay Dean Scientific Officer - Biodiversity
-----Original Message----- From: <email obscured> <email obscured>] On Behalf Of Jim McLeod Sent: Wednesday, 8 April 2009 3:15 PM To: <email obscured> Subject: Re: [dataversity public discussion] Dataversity & IRIS: Notes from the meeting I believe the answer here is that they haven't yet got together the biodata requirements of the IRIS councils, therefore they haven't made a decision on whether or not the ARC / EBOP software fits those requirements.What they are presently (or will shortly be) doing is the prioritisation of functional areas then looking at the needs of those areas. Shay, Jim Lambie - comments? On Wed, Apr 8, 2009 at 2:37 PM, Paul Fisher <email obscured>> wrote: > Jim, > > Many thanks for the IRIS update. Could someone explain why IRIS > members are not interested in existing biodiversity software: the ARC > and EBoP software both have extensible structures that work as > (web-linked) biodiversity packages (?). > > Regards, > Paul > > -----Original Message----- > From: <email obscured> > <email obscured>] On Behalf Of > Jim McLeod > Sent: Wednesday, 8 April 2009 1:55 p.m. > To: <email obscured> > Cc: <email obscured>; <email obscured>; > <email obscured>; <email obscured>; > <email obscured>; <email obscured> > Subject: [dataversity public discussion] Dataversity & IRIS: Notes > from the meeting > > Good afternoon, > > Last Thursday members of Dataversity met with the IRIS Project > Director and an EW Business Analyst to discuss how Dataversity might > work with IRIS. > > The notes and proposed actions from this meeting are attached. > > Questions, comments, suggestions and discussion welcome! > > Cheers > Jim > > > *Dr Jim McLeod*| Regional Data Advocate | Resource Information Group > *Environment Waikato* > P: +64 7 859 0999 > M: 021 369 813 > E-mail: <email obscured> > PO Box 4010, Hamilton East, Hamilton 3247 > > ++++++++++++++++++++++++++++++++++++++++++ > Purpose: To explore how Dataversity might work with IRIS to procure > Biodiversity databases > > Meeting Attendees: > > Bala Tikkisetty (EW RIG Programme Manager) Yanbin Deng (EW > Biodiversity) Ryan Clark (EW Biodiversity)) Beat Huser (EW Strategic > Projects) James Lambie (Horizons) Shay Dean (TRC) Derek Postlewaight > (IRIS Project Director) Tracey Powrie (EW Business Analyst) Jim McLeod > (EW Regional Data Advocate) > > Meeting notes: > > 1. IRIS presently involves six Regional Councils (RCs) (Northland, > Waikato, Horizons, Taranaki, West Coast and Southland). Discussions > are > occurring with two other Regions: Bay of Plenty and Hawkes Bay > 2. IRIS core focus is Regional Council; Monitoring (including > Consent, > Environmental, Biosecurity, Pest, Selected land use, Incident, etc), > Resource > Consents, Enforcement, Incident Tracking, Central Contacts, Dams, > Policy, > Biosecurity, Biodiversity, Customer Service, Land Management, & > selected > Land Use. Common core attributes are the contact and spatial > aspects. > Details are still being worked on collaboratively by the IRIS > Councils. > 3. This core application suite and data will interact with others as > appropriate via Webservices. At present the need for direct > webservice > access to the IRIS data (cf IRIS applications) has not been raised or > considered. > 4. Where appropriate spatial attributes for these data will be > accommodated > 5. The preference was to buy a package, but there was nothing > suitable. > So IRIS is a development project. In setting the scope for that > development, the preference is not to develop duplicate systems or > services where commercial packages are available. IRIS concentrates > on > those requirements RCs have where no commercial product exists. > Currently > IRIS 'buy' is for development tools, not applications, each council > makes > their own application buy decisions outside of IRIS. For example it > is > excepted that each RC will buy its own Finance, Document Management > or > Time-series application. > 6. Much time has been spent negotiating the Council specific > partnership arrangements > including governance and funding structures. > 7. Partners contribute to IRIS funding as a function of six metrics > including the number of staff and number of rate payers, and > financial > capacity. > 8. Agreement has been for a continuing stream of funding for > maintenance and > enhancement of the IRIS application. What happens for new areas of > functionality outside of current scope has not yet been determined. > 9. Development Priorities / sequence are still being determined, but > will be agreed by 1 July 2009. The prioritisation process is > presently > being developed. > 10. Project funding covers Council staff only when they work for the > project office, other than that the project does not cover Council > staff > involvement in the project. > 11. Communication between IRIS and Councils via a circulation list. > One > person in each council has the right to add people to that council's > list. > Each council can decide how they circulate the list within that > council. The list will not be filtered based on the requirements of > an > individual. If you are on the list because of a specific interest, > you get > all the communication, not just your area of interest. > 12. The primary target of the IRIS applications are Regional > Councils. > Some TAs and Unitary functions are unlikely to be provided by IRIS. > > Possible actions for Dataversity members: > > 1. IRIS engages with the Councils, therefore any involvement of > Dataversity would have to be via those Dataversity members whose > Councils > are IRIS partners, and then within the framework of that Council's > needs > and agreed IRIS priorities. IRIS will not engage with Dataversity. > Dataversity > could link with IRIS by coordinating the biodiversity needs within > the > IRIS Councils and then having those Councils collectively advocate > those > needs. (James Lambie to find the Dataversity members who come from > IRIS > Councils.) > 2. In some Councils, Dataversity has members from biosecurity and > from > biodiversity areas. Collaboration between these areas will help > achieve > common goals. (Jim McLeod to discuss with Dan Randow about options > for > connecting these people.) > 3. Dataversity members could collaborate to get TFBIS funding or > Envirolink Funding for biodata in IRIS or funding for a related > initiative to procure a Biodiversity Database/application that > interacts with IRIS via Webservices. (Dataversity IRIS members to > exploreand if appropriate raise with the IRIS Steering Committee > .) > 4. To create Biodata specific applications for Councils, Dataversity > might leverage the IRIS governance and funding mechanisms rather > than create > a parallel structure within Councils. (Dataversity IRIS members to > explore and if appropriate raise with the IRIS Steering Committee. > 5. Communication: Jim McLeod (or an equivalent) should continue to > keep the > Dataversity community updated on progress. Dataversity members of > the IRIS > Councils need to be active in their Council's IRIS to either ensure > that > the biodata aspects are designed in a way that meets their needs or > to > identify gaps that need to be filled. Dataversity IRIS members > should > also report back together and to the IRIS community on best practice > / > tricks of the trade / filling the gaps. > 6. Dataversity IRIS members are interested in being able to combining > data from other organisations with IRIS data. For example DOC data. > Attendees to the IRIS meeting were keen to hear how DOC and other > central > government agencies were progressing with providing access to their > biodata > via Webservices. > > > > > ********************************************************************** > > This email message and any attached files may contain confidential > information, and may be subject to legal professional privilege. If > you have received this message in error, please notify us immediately > and destroy the original message. Any views expressed in this message > are those of the individual sender and may not necessarily reflect the > views of Environment Waikato. Environment Waikato makes reasonable > efforts to ensure that its email has been scanned and is free of > viruses. However, Environment Waikato can make no warranty that this > email or any attachments to it are free from viruses. > > Visit our website at *http://www.ew.govt.nz * > > ********************************************************************** > > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/7wMoHSciexaGSsY9R6Qlr6 > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscri > be > > Start your own free groups and site with OnlineGroups.Net > http://onlinegroups.net You are prohibited from distributing this > E-mail without permission. If you have received this E-mail by mistake > or are not the intended recipient, please notify the sender and erase > the message immediately. This E-mail message and any accompanying > data is confidential and may be legally privileged. The Nelson City > Council does not warrant or guarantee that this communication is free > of errors, virus or interference. > > This e-mail has been scanned and cleared by MailMarshal. > > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/3roMVZnebCjQnSbtBS2mi5 > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscri > be > > Start your own free groups and site with OnlineGroups.Net > http://onlinegroups.net > ----------------------------------------- Full text of this topic in Dataversity Public Discussion: http://dataversity.org.nz/r/topic/TfAn3Z5qV0Qy1ik6JYIn3 To leave Dataversity Public Discussion, email <email obscured>?Subject=unsubscribe Start your own free groups and site with OnlineGroups.Net http://onlinegroups.net Taranaki Regional Council 47 Cloten Road, Private Bag 713 Stratford 4352, New Zealand P: 06 765 7127 F: 06 765 5097 www.trc.govt.nz working with people | caring for our environment ----------------------------------------------------------------------------------- If you are not the intended recipient, any use, distribution or copying of this message is prohibited. Please notify us immediately and erase all copies of this message and attachments. Thank you. Please consider the environment before printing this e-mail.
Computerworld reports that a CCO will be set up to contract with Datacom for IRIS (Integrated Regional Information System). http://computerworld.co.nz/news.nsf/news/F2DFABADA43FAC45CC257607006F2BC9 The six councils involved are: Environment Waikato, Northland Regional Council, Horizons-Manawatu, the West Coast Regional Council, Environment Southland and the Taranaki Regional Council. Can anyone give an update on how biodiversity is being taken into account in the requirements gathering for IRIS?
Dan
Didn't this get covered in Dataversity here http://dataversity.org.nz/groups/dataversity_public_discuss/messages/topic/1u64O0R95uIC56xiYHT14r
On Wed, Aug 5, 2009 at 12:42 PM, <email obscured>> wrote: > Computerworld reports that a CCO will be set up to contract with Datacom > for IRIS (Integrated Regional Information System). > http://computerworld.co.nz/news.nsf/news/F2DFABADA43FAC45CC257607006F2BC9 > > The six councils involved are: Environment Waikato, Northland Regional > Council, Horizons-Manawatu, the West Coast Regional Council, Environment > Southland and the Taranaki Regional Council. > > Can anyone give an update on how biodiversity is being taken into account > in the requirements gathering for IRIS? > > Dan > ----------------------------------------- > Full text of this topic in Dataversity Public Discussion: > http://dataversity.org.nz/r/topic/47RMIZanDZZLC2faywbnPo > > To leave Dataversity Public Discussion, email > <email obscured>?Subject=unsubscribe > > Start your own free groups and site with > OnlineGroups.Net http://onlinegroups.net > > Host your own online groups site with > GroupServer http://groupserver.org >
Jim, > Didn't this get covered in Dataversity here > http://dataversity.org.nz/groups/dataversity_public_discuss/messages/topic/1u64O0R95uIC56xiYHT14r You posted a detailed report on 8 April, Jim. http://dataversity.org.nz/r/post/7wMoHSciexaGSsY9R6Qlr6 I am interested to know of any IRIS developments in relation to biodata that have happened in the four months since then.
Dan
As the press report says, I understand that IRIS has been heavily involved in setting up governance and funding structures. This is not a quick matter for Councils as the Local Government Act requires joint and consistent statements in all the participating Councils' LTTCPs and these issues can soak up much time. As for Biodiversity per se, the opportunity is still for the biodiversity people from the participating Councils to agree their requirements and to individually approach their organisations with consistent requirements. These requirements need to be taken back through the Council management structures, through the IRIS contact points to the IRIS project. This would mean that IRIS would hear a common and consistent biodiversity request. Dataversity, of course, can not approach IRIS but it can be a collaboration forum, for the development of those requirements. So where are the requirements? I have to admit, that this financial year my focus and responsibility has shifted away from IRIS and Geospatial related issues (LGA administration and corporate services), back to the management of natural and physical resources (the RMA side of things).
Jim
Is anyone close to the process for addressing biodiversity data requirements for the IRIS project? Perhaps there is overlap between that and our own Requirements definition efforts. http://dataversity.org.nz/guide/requirements/ For now, there is an overview of progress with IRIS in this Report to Finance & Audit Committee from Environment Waikato. http://www.ew.govt.nz/PageFiles/14065/1579556.pdf This reports the project to be on track, and addressing legal structure and technical architecture issues, with implementation scheduled for 2011. Any other news about IRIS?
Dan
ComputerWorld has published an update on the Integrated Regional Information System (IRIS) joint regional council information services project. http://computerworld.co.nz/news.nsf/news/councils-shoot-for-mid-2011-iris-release The system is a collaboration between Environment Waikato, Northland Regional Council, Horizons-Manawatu, the West Coast Regional Council, Environment Southland and the Taranaki Regional Council, who are forming a new Council Controlled Organisation to own and manage the system. The technical approach being taken is to build a framework that supports tightly linked modules for specific functions. Implementation is expected to be complete by the end of 2011.
Dan
Loading…
Privacy | Acceptable Use | Terms of Service | About OnlineGroups.Net | Contact OnlineGroups.Net
Start an OnlineGroups.Net site for easier email collaboration in your organization.
Powered by GroupServer, the open source web-based mailing list manager.