Hi All,

A quickcross ref to public discussion on the BSS phase one report to make re-finding later easier!.   

http://dataversity.org.nz/r/post/3Gn0xjumU2LBxTaebwiUPC

Regards,
Jim

Hi all
The BSS project is steaming ahead! This is to give you a brief update.
See also the BSS WIKI: https://teamwork.niwa.co.nz/display/NZBSS 

We had a busy two month with 6 workshops up and down New Zealand.
- James Lambie, Horizons Council and Mike McMurty, Auckland Council, have carried online surveys and series of six workshops across the country to collect information for the terrestrial and infrastructure work streams.

- The material collected from the workshops and the online survey is currently written up into draft reports on the terrestrial and freshwater use cases for the July BSS Steering Committee meeting. 

- A ‘strawman’ for a ‘BSS exchange format’ was developed through the workshops. Purpose of the ‘strawman’ is to identify key information components to be transported through the BSS infrastructure to satisfy (most of) the use-cases.

- Purpose of the BSS Steering Committee meeting on July 23rd is to discuss and to endorse the draft reports and the developed ‘strawman’. We will then make the material available to the wider community for comments. Stay tuned!

More detailed guidance will be provided after the workshops in July/August. We
plan to run dedicated implementation workshops with data providers during
September-November.

Happy BSSing! Jochen

Hi all
The BSS project is steaming ahead! This is to give you a brief update.

This month is "BSS workshop" month. 
We are conducting 5 workshops around the country to fine-tune BSS requirements. 
See BSS web page: https://teamwork.niwa.co.nz/pages/viewpage.action?pageId=27983920

How to get "BSS ready"? - Initial guidance
We are now much clearer on the BSS requirements. Therefore I have provided some initial guidance for data providers to get "BSS ready":
Information on existing services and tools for federation of biodata. https://teamwork.niwa.co.nz/display/NZBSS/Information+on+existing+services+and+tools+for+federation+of+biodata
Hints for data providers to get "BSS ready". https://teamwork.niwa.co.nz/pages/viewpage.action?pageId=30179771
Bio data management in NZ: Options. https://teamwork.niwa.co.nz/display/NZBSS/Bio+data+management+in+NZ%3A+Options

More detailed guidance will be provided after the workshops in July/August. We plan to run dedicated implementation workshops with data providers during September-November.

Happy BSSing! Jochen

Hi all
To support communication in our BSS project I have created a simple webpage as a reference to core information and to advertise upcoming events and news:

https://teamwork.niwa.co.nz/display/NZBSS 

If you have any requests / suggestions on content please contact me.

Regards, Jochen

Hi all
I believe I never posted the actual final report for TFBIS project 282.
Find attached.

Apologies. Jochen

I like to report on our Progress with the BSS project.

We have agreed on a plan for the Terrestrial and Freshwater Use Cases work streams.

James Lambie, Jerry Cooper, and Mike McMurty have agreed to work jointly on these work streams with the following timeline:

-	We will work on a notification and template for gathering information on the uses cases and will distribute this amongst the community within March.
-	We will conduct a number of workshops throughout the country inviting data providers and data users to gather face-to-face input. 
-	A first draft of a report on use-cases will be written up by end of July and distributed for comments and review.
-	If necessary a 2nd workshop phase is planned in October/November for refinements.
-	Final report on use cases is due December.

Any questions please get back to me.

I trust you all support the project team throughout this year in their endeavour to  work towards a federated biodata future!

Regards, Jochen

Jochen and all,

Here are my thoughts about the project process for BSS.

1 BSS will need to be social as well as technical. This applies not just to the process of getting BSS going (Jochen knows this well and is doing wide engagement) but it applies to the ongoing process of sharing actual data using BSS when it is built. For all the standards and tools and pipes we can build, the data will still be messy and odd, and often closely held. It will be highly dependent on people and conversations to get it shared and usefully consumed. BSS will have to have mechanisms to support the social processes that go along with the technical data sharing processes.

2 Technically, BSS may involve hand-wrangled data (at least in its early stages).

3 BSS should be implemented in stages. With a complex thing like a biodata-sharing network, it is very difficult to know what works or doesn't without people actually trying it. If BSS is rolled out in one big go at the end of one big design process it will be more likely to fail. Releasing early prototypes and iterating based on feedback will make it more likely to succeed.

Hi all
Thanks very much for a very inspiring and productive dataversity workshop last week!
I felt great cohesion and progress.
Please find attached the write-up from the use-case workshops. This will give the BSS project a head start! 
(Dan: could you please put in the dataversity workshop google docs folder. thanks)

Regards, Jochen

Because by mistake I hid Jochen's original post and the TFBIS proposal 
(sorry). Here it is again.

Hi all
Please find attached a summary of the BSS project on two pages.

Regards, Jochen

Good suggestions Brent

I especially like Biota - a simple name that describes the data. Doesn't need to be an acronym for a longer name. If we need a NZ label, then NZBio or Biotanz.

SPecies Observations NZ (SPONZ) also good.

However, have to confess that a bit of humour goes a long way so I do like SPOCK!

Cheers
Barb

A few thoughts... that I'm brave enough to share :-)


BIOdiversiTy Aotearoa
or
BIOdiverstity Terminus Aotearoa
for BIOTA?

BIOdiverstity Centre for Aotearoa
= BIOCA

SPEcies Centre of Knowledge
= SPECK

for trekkies: SPecies Observations Centre of Knowledge

:-)


SPecies Observations NZ
= SPONZ



Cheers

Brent

How about 'what lives where' ?

Andrew

On 5/09/13 6:05 PM, "Colin Meurk"  wrote:

>I definitely wouldn't have the word 'national' in there - or 'labour' for
>that matter :-).  Let's try something more neutral like 'nz life map' etc
>or 'life map aotearoa'.  Always check out the initials too and what they
>may stand for.
>c
>
>-----Original Message-----
>From: interoperability@dataversity.org.nz
>[mailto:interoperability@dataversity.org.nz] On Behalf Of Ravi Shamihoke
>Sent: Thursday, 5 September 2013 1:28 p.m.
>To: 'interoperability@dataversity.org.nz'
>Subject: Re: [interoperability] Name for the Project
>
>I'm not a bio-xyz literate person, just some one who works in IT and
>understand bits of what biosecurity divisons do, so by no means am any
>sort of expert
>
>Interpreting what I have read so far
>
>SpIDS - Species Interoperability Data Store
>
>Occupancy is just a showcase, so it doesn't need to be part of the
>branding, best left inside a domain model if I'm correct in saying that
>
>Things like services stack are best left inside the architecture than
>exposed in the branding
>
>So SpIDS-version1 can be the Occupancy showcase
>
>
>-----Original Message-----
>From: interoperability@dataversity.org.nz
>[mailto:interoperability@dataversity.org.nz] On Behalf Of Jochen Schmidt
>Sent: Thursday, 5 September 2013 12:12 p.m.
>To: interoperability@dataversity.org.nz
>Subject: Re: [interoperability] Name for the Project
>
>Thanks Dan
>for kicking that off and explaining the naming clearly.
>Aside from non-native speaker I consider myself very bad with names and
>branding and would like to leave it to the community how we call this
>"baby"
>Jochen
>
>-----Original Message-----
>From: interoperability@dataversity.org.nz
>[mailto:interoperability@dataversity.org.nz] On Behalf Of Dan Randow
>Sent: Wednesday, 4 September 2013 6:33 p.m.
>To: interoperability@dataversity.org.nz
>Subject: [interoperability] Name for the Project
>
>
>Hi All, and congratulations to Jochen and the others involved in getting
>the Interoperability AKA Biodata Services Stack AKA Species Occupancy
>data project  up
>and running!
>
>I have been giving a little though to the name of the project. It could
>appear that it has three names, none especially compelling.
>
>Actually, the three names reflect different things.
>
>The overall goal of the project is to demonstrate the benefits and
>feasibility of data *interoperability*.
>
>That will be done by building a showcase. *Species* *Occupancy* data has
>been chosen as a showcase as it is easy to see how useful it is.
>
>The means of building the showcase is a Biodata Services Stack (*BSS*).
>
>Would it make sense to use a single compelling name to communicate this
>project to the stakeholders, even while it is work-in-progress?
>
>Neither BSS nor Interoperability are especially compelling. Species
>Occupancy has been chosen because it is compelling. It is a *data*
>project tho, not an actual occupancy project.
>
>So could we call the intended output what it is, a "Species Occupancy
>Data Platform" ("SODP"?). I suggest no.
>
>How about something along the lines of "National Species Map"? (I promise
>it is a complete coincidence that it is a translation of "Atlas of Living
>Australia"). We already have a "Living Aotearoa"
>.
>
>Dan
>
>-----------------------------------------
>Full text of this topic in Interoperability:
>http://dataversity.org.nz/r/topic/3Ng7bfvYOrZyrWhuZjkC3
>
>To leave Interoperability, email
>mailto:interoperability@dataversity.org.nz?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
>--
>Please consider the environment before printing this email.
>NIWA is the trading name of the National Institute of Water & Atmospheric
>Research Ltd.
>
>-----------------------------------------
>Full text of this topic in Interoperability:
>http://dataversity.org.nz/r/topic/6VRvKPtXROKyHTiFjWADR1
>
>To leave Interoperability, email
>mailto:interoperability@dataversity.org.nz?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
>
>##########################################################################
>###########
>This e-mail message has been scanned for Viruses and Content and cleared
>by NetIQ MailMarshal
>##########################################################################
>###########
>
>__________________________________________________________________________
>____
>
>This email has been filtered by SMX.
>For more information visit http://smxemail.com
>__________________________________________________________________________
>____
>
>
>-----------------------------------------
>Full text of this topic in Interoperability:
>http://dataversity.org.nz/r/topic/3I1KSjrgfR13eEoPN6uZKS
>
>To leave Interoperability, email
>mailto:interoperability@dataversity.org.nz?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
>
>________________________________
>
>Please consider the environment before printing this email
>Warning: This electronic message together with any attachments is
>confidential. If you receive it in error: (i) you must not read, use,
>disclose, copy or retain it; (ii) please contact the sender immediately
>by reply email and then delete the emails.
>The views expressed in this email may not be those of Landcare Research
>New Zealand Limited. http://www.landcareresearch.co.nz
>
>-----------------------------------------
>Full text of this topic in Interoperability:
>http://dataversity.org.nz/r/topic/5KvosDHd2A0fWaW6QmOWlY
>
>To leave Interoperability, email
>mailto:interoperability@dataversity.org.nz?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

I definitely wouldn't have the word 'national' in there - or 'labour' for that matter :-).  Let's try something more neutral like 'nz life map' etc or 'life map aotearoa'.  Always check out the initials too and what they may stand for.
c

I'm not a bio-xyz literate person, just some one who works in IT and understand bits of what biosecurity divisons do, so by no means am any sort of expert

Interpreting what I have read so far

SpIDS - Species Interoperability Data Store

Occupancy is just a showcase, so it doesn't need to be part of the branding, best left inside a domain model if I'm correct in saying that

Things like services stack are best left inside the architecture than exposed in the branding

So SpIDS-version1 can be the Occupancy showcase

Thanks Dan
for kicking that off and explaining the naming clearly.
Aside from non-native speaker I consider myself very bad with names and branding and would like to leave it to the community how we call this "baby"
Jochen

Hi All, and congratulations to Jochen and the others involved in getting the Interoperability AKA Biodata Services Stack AKA Species Occupancy data project  up and running!

I have been giving a little though to the name of the project. It could appear that it has three names, none especially compelling.

Actually, the three names reflect different things.

The overall goal of the project is to demonstrate the benefits and feasibility of data *interoperability*.

That will be done by building a showcase. *Species* *Occupancy* data has been chosen as a showcase as it is easy to see how useful it is.

The means of building the showcase is a Biodata Services Stack (*BSS*).

Would it make sense to use a single compelling name to communicate this project to the stakeholders, even while it is work-in-progress?

Neither BSS nor Interoperability are especially compelling. Species Occupancy has been chosen because it is compelling. It is a *data* project tho, not an actual occupancy project.

So could we call the intended output what it is, a "Species Occupancy Data Platform" ("SODP"?). I suggest no.

How about something along the lines of "National Species Map"? (I promise it is a complete coincidence that it is a translation of "Atlas of Living Australia"). We already have a "Living Aotearoa" .

In 2012, Te Papa was funded by TFBIS to carry out a small project on the
museums perspective to biodiversity datasharing, in the online environment. The
results of our extensive interviews, and online demo site are discussed here:
http://www.tepapa.govt.nz/ResearchAtTePapa/Research/NaturalEnvironment/Pages/Overview.aspx

We worked with most of you! Thanks for all your help and ideas! Atlas of Living
Australia gave us a huge hand out and helped build a site to try out some
concepts of sharing data ALA style in the New Zealand context.

This is accessible via this url http://livingaotearoa.ala.org.au/
(updated since yesterday)

Love to hear some feedback.

In 2012, Te Papa was funded by TFBIS to carry out a small project on the museums perspective to biodiversity datasharing, in the online environment. The results of our extensive interviews, and online demo site are discussed here:
http://www.tepapa.govt.nz/ResearchAtTePapa/Research/NaturalEnvironment/Pages/Overview.aspx

We worked with most of you! Thanks for all your help and ideas! Atlas of Living Australia gave us a huge hand out and helped build a site to try out some concepts of sharing data ALA style in the New Zealand context. 

This should be accessible via this url (I just checked, and its not 'up' at present) http://www.livingaotearoa.ala.org.au/

Love to hear some feedback.

Dear biodata enthusiasts
This is to let you know that TFBIS has decided to fund a project which I put together with Landcare, DOC, and Regional Councils for building a "biodata services stack".

Among other things the proposal says: 
This project, based on TFBIS Scoping Report 282, has the goal to develop national solutions for mobilising access to primary biodiversity data through a federated data network. This work supports local, regional, and national conservation management and national monitoring and reporting. The network delivers multiple benefits beyond conservation management and facilitates biosecurity risk assessment for invasive species, pests and pathogens. Consistent, quality-assessed national biodata supports research, the Environment Domain Plan, international obligations through GBIF and GEO-BON in support of the Intergovernmental Platform on Biodiversity and Ecosystem Services (IPBES), and is a fundamental contribution to a national Clearing House Mechanism.
...
The explicit goal of the project is to develop tools and infrastructure components to increase interoperability between biodata sources. We call this infrastructure as a whole the ‘Biodata Services Stack’.

I am working on a project plan and implementation and will keep you posted.

Best. Jochen