ices-tools-dev / biodiversity-portal Goto Github PK

There is a difference in the IA 2017 areas compared to the normal OSPAR boundaries. It is mainly an issue in the Kattegat so it could be a non issue for Seals and Birds if this area contains no data. So would just like to have your opinion and then we can tick it off.

Facilitate full-dataset resubmissions: create respective data checks; facilitate the ‘assessment data snapshots’

@ospar-odims revise this pdf

• Check present default data access type in the last data call.

• Notify data submitters on B3 data delivered until now not flagged by any data access type

JWGBird report (2016), section 5.1.5:
"The data providers in JWGBird would appreciate some immediate feedback from the database when they upload data. ICES are currently developing a summary record that data providers will receive immediately after submission and will enable them to check if all data were uploaded correctly. The summary record could include a list of species for each data type (i.e. non-breeding abundance, breeding abundance, breeding success), time-span of dataseries, number of sites, etc. Furthermore, it may be useful to compare the latest update with the summary records from the previous updates. "

In the portal, make the links more visible

Hi - I am trying to export and upload the last data from spain and portugal but both data sets include species not in the vocabulary. How do I add them so that the XML macro works?
The new species are:
1488274 Chroicocephalus genei Slender-billed Gull
137191 Hydrobates castro Band-rumped Storm-petrel
137139 Larus audouinii Audouin’s Gull

for Ian: to provide ICES with the contacts interested in this function
for ICES:

• Develop a procedure for automated fill-in of counts with zeroes for mot modelled observations. Key: Survey, species, year
• Dialogue with the key submitters
• Implement the feature

The question of partial submissions and resubmissions was not handled properly for seals yet.
We've had an impression that one data call submission is to be expected from each reporting country/institute.
Now we received 5 partial submissions from the UK.
Advice is needed on whether partial resubmissions are to be allowed, and what would be the key for resubmissions.

Different organisations used the same code for completely different sites. This meant that some count data were attributed to the wrong sites in the database.
This has been addressed by ICES by making a unique key based on NationalColonyID and EDMO code (which uniquely defines each organization). Thus each organisation within a country has governance over its own sites.
However, permanent solution is pending implementation in the DB

Revise the ‘Guidance’ document based on recent changes in format and features (ICES) and decisions (Ian)

Cancelled
Chroicocephalus genei is the Mediterranean species that would not be included to the indicators. Submitters can still upload the data, if they want (by editing the local copy of the Template

• Add field ‘SurveyID’ to the ‘Birds_site_description’
• Make ‘B1_Abundance_data’ optional, or make 2 separate submission forms for B1 and B3
• Add ‘Data_access’ field to the ‘B3_Breeding_success’

for Ian: to collect information and provide instructions on which data entries should be changed and how
for ICES: to change the submission files, notify national submitters, re-upload data.

for the data call of birds we have a template we need to test,

also it is important to:

1. test the file with some data, we need to be sure that is working correctly and the more people it test the better.

2. not to include the file in the datacall, instead include a link to the template in the data call (http://ices.dk/marine-data/Documents/biodiversity/OSPAR_Birds_Reporting_Format.xlsm)
   The reason for this is that if there is any change (in field type or vocabs) then we can still correct it, while if you include it in the data call it won’t give us any change of correcting it.

Has there been agreed on frequency for data calls?
Has it been agreed on the dates for the next data call?

November

• (OSPAR) OMMEG Seals meets Nov 16: clarification on outstanding questions;
• Assessment Units to be clarified (defined)
• Finalize guidance
• Finalize format

End November

• Draft of generic restricted licence
• Data call published

December

• Additional validation checks to be established

February 2021

• Data submission deadline

September 2021

• Indicator drafted

On the landing page, add a password-protected action button for browsing individual submissions

[low priority]
for JWGBirds:
Bring-up the recommendation to the [COBAM] meeting for further discussion
for ICES:
Investigate possibilities for direct data harvesting

We got very close to finalizing the data format with Nora before she left her position, however we now need to pick this up and validate afresh before we can move forward with the seals part of the biodiversity database

There are public and restricted records in the biodiv database. It was agreed in the initial specification that the main entry point to data outputs would be the OSPAR assessment and data systems. Therefore ICES need to provide a secure web service so that OSPAR can request the data and then publish via ODIMS/OAP in the format they require

Share thoughts on potential workshops

Only some of the existing data gathered is usable in the form that feeds the indicator. It might be best to finalize the format (separate issue) and then instigate a new data call - to be discussed.