CETAF ISTC Wiki - User contributions [en]

Main Page

2026-02-24T07:53:45Z

D.Fichtmüller: numbering of Table of Content disabled

<div class="noautonum">__TOC__</div>

= CETAF Information Science & Technology Commission (ISTC) =

'''''Developing technical services for our community'''''

The Information Science & Technology Commission (ISTC) facilitates dialogue and collaboration between the IT departments of CETAF member and non-member institutions to ensure institutional interoperability through the development of common infrastructures and standards. The group works towards compatibility of components for digital information exchange and sharing, through procedural changes and adaptations to IT systems.

Members of the ISTC officially represent IT or Biodiversity Informatics departments of [https://cetaf.org/ CETAF] institutions. The group was established as a technical working group of the EU-funded project European Distributed Institute of Taxonomy ([https://cordis.europa.eu/project/id/18340 EDIT]) and was integrated into CETAF in 2011.

== Who we are & how we collaborate ==
[[Members]] 
[[Working Group Charter]] 
[[Meetings]] 

== ISTC Subgroups ==
Natural Science Collections and AI 
[[Collection Management Systems]]

== Important ISTC products ==
[[CETAF Stable Identifier Guide|CETAF IDs]] 
[[IIIF]] Recommendation 
[https://services.bgbm.org/botanypilot/ Botany Pilot]

== Other activities ==
[[Research Data Management in CETAF member organisations]] 
[[Storytelling with IndExs]]

Working Group Charter

2025-08-11T08:22:02Z

D.Fichtmüller: turn of numbering for table of content

= Working Group Charter – CETAF ISTC =
<div class="noautonum">__TOC__</div>

== 1. Purpose and Vision of the Working Group ==
The Information Science & Technology Commission (ISTC) was established as a technical working group of the EU-funded project European Distributed Institute of Taxonomy (EDIT) and was integrated into CETAF in 2011. It facilitates dialogue and collaboration between the IT departments of CETAF member and non-member institutions to ensure interoperability through the development of sustainable common informatics infrastructures, best practices recommendations, and standards. The group works toward compatibility of components for digital information exchange and sharing, through procedural changes and adaptations to IT systems. The ISTC plays an essential role in knowledge transfer between CETAF member organisations, in ensuring the sustainability of data services and the widest possible use of existing open-source software components. An important aspect is the planning and facilitation of collaborative projects between CETAF informatics departments.

== 2. Strategic Relevance to CETAF ==
The ISTC supports CETAF’s strategic priorities by promoting open access policies and collaboration on digitization efforts to increase the accessibility of natural science collections. By fostering technical innovation and collaboration, ISTC contributes to CETAF's mission of addressing biodiversity and geodiversity challenges.
An important contribution to the strategic goals of CETAF is, in particular, the support provided to smaller institutions in the transformation of analog collections and research processes into digital infrastructures.

== 3. Main Themes and Objectives ==
The main topics of the ISTC are currently
# the development of a global registration system for type specimens (in cooperation with TETTRIs),
# Collection Management Systems (CMS),
# AI, robotics, and digital collections, and
# collaboration between citizen science platforms.

Specific objectives include 1) a proof of concept for a wiki-based type specimen catalogue and 2) a coordinated approach (e.g. with GBIF and DiSSCo) for the sustainable development of this catalog. Another objective is the development of a programme for the newly created sub-groups for CMS and AI.

== 4. Work Plan and Deliverables ==
2025/Q2: ISTC charter agreed. 
2025/Q3: Subgroup “AI, robotics and digital collections” established. 
2025/Q3: Subgroup “Collection Management Systems” established. 
2026/Q1: Proof of concept for Type Specimen Catalogue communicated.

== 5. Evaluation and Success Metrics ==
The success of the ISTC can be measured by specific products that have emerged from the group's work. Prominent examples in the past were the CETAF Identifier specification, the CETAF IIIF recommendation, the “Botany Pilot” and (in collaboration with TETTRIs) joint missions of citizen science platforms.
The ISTC is not seeking to establish evaluation criteria in the form of KPIs.

== 6. Timeline and Lifetime ==
ISTC is a permanent CETAF working group.

== 7. Roles and Responsibilities ==
The ISTC Coordinator(s) organise and moderate the working group's general meetings, establish communication with the CETAF EC and CETAF working groups, maintain the communication platforms used and support the subgroups and task groups in their work.
Conveners of ISTC subgroups are responsible for developing the scope, membership, and work plan for their subgroup. They report to the ISTC plenary.
The ISTC Plenary decides on the medium-term work plan and the establishment of thematic subgroups.

== 8. Governance and Decision-Making Structure ==
The ISTC does not have a formalized governance structure. Decisions are made by consensus. The ISTC would be open to discussing and adopting joint governance structures for all CETAF working groups.

== 9. Communication and Collaboration Tools ==
The main communication platform of the ISTC is the ISTC wiki at https://istc.cetaf.org/Main_Page, presently hosted and curated by FUB-BGBM. The wiki documents important ISTC products, RDM-related and data policies by CETAF members (in preparation), and meeting minutes. The ISTC uses an email list hosted by CETAF.

== 10. Stakeholder Engagement (Internal & External) ==
The ISTC collaborates closely and occasionally holds joint meetings with the Digitization Working Group (DWG). The ISTC is strongly connected to standardisation and infrastructure initiatives such as TDWG, DiSSCo, and GBIF. Collaborations are established via joint projects and mutual participation in meetings. The ISTC is open for participation of external experts both in the meetings and the Email list.

== 11. Resource Planning – Human, Technical, Financial ==
The critical resource for cooperation in the ISTC is the available working time of its members and the coordination. For this reason, many activities are opportunity-driven and are promoted, for example, in the context of funded EU projects. It is therefore difficult to draw up work plans that function independently of project funding. However, it is possible and desirable to integrate ISTC topics into project proposals.
Potential support for ISTC would be mainly at the organisational level, for example, in planning and organising meetings.
== 12. Appendices ==
The ISTC does not currently maintain a curated list of members. We therefore consider the members of the email list to be ISTC members.

MediaWiki:Common.css

2025-08-11T08:21:27Z

D.Fichtmüller: /* selectively disable numbering for tables of content */

/* CSS placed here will be applied to all skins */

/* inline definitions */
.definition-inline dt { float:left; padding-right:0.5em; margin-bottom: 0px; line-height: 1.5em;}
.definition-inline dd { margin-bottom: 0px;line-height: 1.6em;} /* line-height a bit higher, because dt in bold pushes line-height */
.definition-inline.code-bold-only dt { font-weight:normal; }
.definition-inline.code-bold-only dt code { font-weight:bold; }

/* 2 column Layout */
.two-columns {
-moz-column-count:2; /* Firefox */
-webkit-column-count:2; /* Safari and Chrome */
column-count:2;

-moz-column-gap:40px; /* Firefox */
-webkit-column-gap:40px; /* Safari and Chrome */
column-gap:40px;

-moz-column-rule:2px outset gray; /* Firefox */
-webkit-column-rule:2px outset gray; /* Safari and Chrome */
column-rule:2px outset gray;
}
/* 3 column Layout */
.three-columns {
-moz-column-count:3; /* Firefox */
-webkit-column-count:3; /* Safari and Chrome */
column-count:3;

-moz-column-gap:40px; /* Firefox */
-webkit-column-gap:40px; /* Safari and Chrome */
column-gap:40px;

-moz-column-rule:2px outset gray; /* Firefox */
-webkit-column-rule:2px outset gray; /* Safari and Chrome */
column-rule:2px outset gray;
}
.three-columns.flat-ul ul li {
float:left;
margin-left:1.5em;
}
.three-columns.flat-ul ul {
clear:both;
margin:0px 0px 0.5ex 0px;
padding:0px;
}
.three-columns.flat-ul p {
margin:5px 0px 0ex 0px;
}
.three-columns tr {
/* verhindere Spaltenumbruch */
-webkit-column-break-inside: avoid; /* Chrome, Safari */
page-break-inside: avoid; /* Theoretically FF 20+ */
break-inside: avoid-column; /* IE 11 */
}

/* booktable as in (scientific) books/journals */
table.booktable, table.booktabledotted {
margin: 1em 1em 1em 0;
background: #ffffff;
border-top: 2px #656463 solid;
border-bottom: 2px #656463 solid;
border-collapse: collapse;
}
.booktabledotted td {
border-bottom: 1px dotted gray;
padding:0.2em;
}
.booktable td {
border: 0px none !important;
padding:0.2em;
}
.booktable tr.line-t td, .booktable tr td.line-t{
border-top: 1px #656463 solid !important;
}
.booktable tr.line-b td, .booktable tr td.line-b{
border-bottom: 1px #656463 solid !important;
}
.booktable tr.line-tb td, .booktable tr td.line-tb{
border-bottom: 1px #656463 solid !important;
border-top: 1px #656463 solid !important;
}
.booktabledotted th, .booktable th {
vertical-align:bottom;
border-bottom:1px solid #656463;
border-top: 1px solid #656463;
border-left:0px;
border-right:0px;
padding: 0.2em;
}
.booktabledotted th, .booktable th {
background: #ffffff;
text-align: center;
}
.booktable caption, .booktabledotted caption {
font-weight: normal;
}
/* a plain table but vertical align top */
table.vertical-align-top td { vertical-align:top;}
table.vertical-align-bottom td { vertical-align:bottom; }
table.vertical-align-middle td { vertical-align:middle; }

/* references hanging layout */
div.hanging-indent {
padding-left:1.5em !important;
text-indent:-1.5em;
margin-top: 0.0em !important;
margin-bottom: 0.0em !important;
}

div.hanging-indent.compact-references p {
margin:0;
}

div.hanging-indent p *
, div.hanging-indent div *
, div.hanging-indent ol *
, div.hanging-indent ul *
{
text-indent:0;
}

/* nesting on talk pages
idea: border only each 2nd level down, not each level down
*/
.ns-talk .mw-body-content ul li > dl {
border-left:blanchedalmond 2px solid;
}
.ns-talk .mw-body-content ul li > dl > dd > dl > dd > dl {
border-left:navajowhite 2px solid;
}
.ns-talk .mw-body-content ul li > dl > dd > dl > dd > dl > dd > dl> dd > dl {
border-left:burlywood 1px solid;
}

.ns-talk .mw-body-content p ~ dl {
border-left:blanchedalmond 2px solid;
}
.ns-talk .mw-body-content p ~ dl > dd > dl > dd > dl {
border-left:navajowhite 2px solid;
}
.ns-talk .mw-body-content p ~ dl > dd > dl > dd > dl > dd > dl> dd > dl {
border-left:burlywood 1px solid;
}

/* for gray line numbers in:
<syntaxhighlight class="lineno-gray" lang="..." line >
</syntaxhighlight>
*/
.lineno-grey span.lineno,.lineno-gray span.lineno {
color:gray;
}

/* selectively disable numbering for tables of content */
.noautonum .tocnumber { display: none; }

2025 Spring Meeting

2025-04-29T10:59:20Z

D.Fichtmüller: added missing names to participant list

= CETAF Information Science & Technology Commission - Spring 2025 Meeting =
'''Bonn, April 7-8 2025'''
== Venue ==
Leibniz Institute for the Analysis of Biodiversity Change 
Museum Koenig 
Raiffeisenhaus 
Adenauerallee 127 
53113 Bonn, Germany
(First floor, on the right. Please follow the signs!)

== Participants ==
* Anton Güntsch (FUB-BGBM, DE)
* Dominik Röpert (FUB-BGBM, DE)
* David Fichtmüller (FUB-BGBM, DE)
* Quentin Groom (Meise Botanic Garden, BE)
* Mathias Dillen (Meise Botanic Garden, BE)
* Maarten Trekels (Meise Botanic Garden, BE)
* Jiri Frank (NM, CZ)
* Adam Cironis (NM, CZ)
* Wouter Addink (Naturalis, NL)
* Dagmar Triebel (SNSB, DE)
* Stefan Seifert (SNSB, DE)
* Sabine von Mering (MfN, DE)
* Caitlin Thorn (MfN, DE)
* <s>Jonas Grieb (SGN, DE)</s>
* Claus Weiland (SGN, DE)
* <s>Anke Penzlin (SGN, DE)</s>
* André De Mûelenaere (Africamuseum, BE)
* Franck Theeten (Africamuseum, BE)
* Björn Quast (LIB, Bonn, DE)
* Birgit Rach (LIB, Bonn, DE)
* Cristina Garilao (LIB, Hamburg, DE)
* <s>Laura Tilley (CETAF, BE)</s>
* Ana Casino (CETAF, BE)
* Glorioso Alessio (CETAF, BE)
* Nicky Nicolson (Kew, UK)
* Arianna Salili-James (NHM, UK)
* Theary Ung (MNHN, Paris, FR)
* Laurent Gohy (ULiège, BE) - first day
* Alex (CETAF)
* Robin Drinkwater (RBGE, Edinburgh)

== Agenda ==
{| class="wikitable"
!colspan="2" | ------------------------------------------------------------ Day 1 - April 7 ------------------------------------------------------------
|-
| '''12:00 - 13:00''' || '''Arrival and lunch'''
|-
| 13:00 - 13:30 || Welcome, introduction of participants, agenda, logistics
|-
| 13:30 - 14:00 || The new ISTC Wiki and future ISTC documentation
|-
| 14:00 - 15:15 || CMS Subgroup - Introduction of the new subgroup - Presentations of CMS-related activities in CETAF collections * [https://istc.cetaf.org/images/1/15/01_theeten_presentation_isct_2025.pdf Frank Theeten] * [https://docs.google.com/presentation/d/1f_mICa50WKusn94CXW0IhELABTsx4IkV/edit?usp=sharing&ouid=114384447688591455468&rtpof=true&sd=true/ Maarten Trekels] * [https://istc.cetaf.org/File:03_Seifert-ISTC-2025-04-07.pdf Stefan Seifert] * <s>Jonas Grieb</s> * [https://istc.cetaf.org/images/8/89/2025-04-07_JACQ_ISTC_Bonn.pdf Dominik Röpert] - Discussion of possible activities of the CMS subgroup and structuring of the collaboration
|-
| '''15:15 - 15:45''' || '''Coffee break'''
|-
| 15:45 - 17:00 || [https://docs.google.com/presentation/d/1UdHPtT6nYadYRgZjgOPMgDlTksrdO-CrbhMgFswh2YM/edit?usp=sharing/ AI, Robotics and Digital Collections Subgroup] - Introduction of the new subgroup - Examples of currently ongoing initiatives - Discussion of possible activities of the AI subgroup and structuring of the collaboration
|-
| 17:00 - 17:30 || Cancelled: <s>Establishment of a new Center for Knowledge Literacy and Biodiversity Informatics at the LIB (Peter Grobe)</s>
|-
| '''17:30''' || '''End of day one'''
|-
| ''19:00 -'' || ''Dinner at Tuscolo, [https://www.openstreetmap.org/?mlat=50.73294&mlon=7.09964#map=16/50.73294/7.09964 Gerhard-von-Are-Straße 8], 53111 Bonn (self paid)''
|}

{| class="wikitable"
!colspan="2" | ------------------------------------------------------------ Day 2 - April 8 ------------------------------------------------------------
|-
| 9:00 - 10:00 || [https://docs.google.com/document/d/1gnCnZgJml1dKllMoK62A8l5x93Hpmbse9Cd80TVzl98/ Type specimen initiative]
|-
| 10:00 - 11:00 || Guided tour
|-
| '''11:00 - 11:20''' || '''Coffee break'''
|-
| 11:20 - 12:20 || Misc presentations (projects, initiatives, ideas, ...): - Indexing of research expeditions and linking to semantic entities (Sabine von Mering) - Cancelled: <s>Enhancing geological specimen data (Laura Tilley)</s> - [https://docs.google.com/presentation/d/1jQp0TKJhnbKCG_IHmNmQaIHOKTQIN7GAbQbsMx-The8/edit?usp=sharing Update on MAS development in DiSSCo] (Wouter Addink) - Exsiccata series in botanical and mycological collections: [[Storytelling with IndExs|Storytelling]] with [http://indexs.botanischestaatssammlung.de/ IndExs], demo (Dagmar Triebel)
|-
| 12:20 - 12:45 || [https://docs.google.com/presentation/d/1Y4VsXEjCGDRzL7_fEMRYpqcgiD-9WUey/edit?slide=id.p2#slide=id.p2 Funding opportunities]
|-
| 12:45 - 13:00 || AOB
|-
| '''13:00''' || '''End of meeting (and packet lunch)'''
|}
== Minutes ==
=== Day 1 ===
==== The new ISTC Wiki and future ISTC documentation ====
==== CMS Subgroup ====
* Presentations are linked in the agenda
* Question to Maarten: Can the tender for their new system be published? Answer: Tender contains some confidential data, but once this has been cleared, it can be shared.
==== AI, Robotics and Digital Collections Subgroup ====
* Presentation is linked in the agenda
* Presentation by Maarten:
** DiSSCo Flanders: second phase with a stronger emphasis on specimen enrichment
** Some work done at University Ghent
** Common steps: straightening, segmenting, multi plant detection, Label OCR, Leaf extraction, identifications for specimen without any (or only rough)
** Future ideas: morphological feature extraction
* Laurent (digitization manager at University Liege): Automating Herbarium Sheet Data Extraction with AI
** specimen QR-Code photographed with camera
** directly read label information with Google Lens
** separate the labels in fields in next step
* Arianna: AI at the [Natural History] Museum [UK]
** topics AI for Digitization / collection
*** Use Cases: General Knowledge Base, based on all information in the collection, trait recognition, insect digitization,
*** Robotic Arm for pinned objects: scan drawer, recognize pins, select pin for handling, move it to photography station, take images of insect from multiple angles and label
** NHM AI Lab (also for general science questions),
*** E.g. Classifications for animal hair or diatoms,
*** Outreach via AI Coffee Lab or Hybrid Lunches, collaboration with the Turing Institute and UCL
** DCMS x NHM AI Pilot program (UK Department for Culture, Media and Sport)
*** People could propose projects, 5 selected.
*** Topics: herbarium: chat bot that answers from the perspective of a known collector
*** Segmentation and part
*** Data extraction based on old index cards
*** AI Alt text Generation
*** Predict species of reptiles based on confiscated fashion products: is the product illegal or not
* General Discussion/Next Steps (sorted by the questions suggested by Arianna)
** What is currently going on, in your institutions?
** What are hurdles to AI techniques?
*** Questionable moralities of the companies behind the LLMs (Copyright?)
*** Power consumption
*** Local or OpenSource LLMs as an alternative?
** How can robotics benefit digital collections?
** How can CETAF facilitate this better?
*** Big wins come from scaling it up to millions of specimen instead of just a couple of ones.
*** Run tools on all of CETAF collections, e.g. search for the signature of a collector
*** DiSSCo Machine Annotation service could help to move the data out of silos
*** This group could help with comparison of the different approaches, quality checks. This could be done on a benchmark subset, but will require a lot of work for a high quality ground truth. Can the creation of this dataset be automated?
*** Maybe additional funding as a COST action? Relevance?
*** Infrastructure requirements: who does this
*** Use Case: Structure unstructured data, could be relevant for the GBIF Capacity Enhancement Program, WFO and PlantNet have a similar approach.
** Mode on which the working group will operate
*** Many colleagues are working on it, but not in particular projects, general interest to continue.
*** How to keep in touch. Slack channel? Free channels will lose old posts.
*** Google Spreadsheet to have an overview who is working on what.
*** Github group
*** DiSSCo will have Hackathons for the Machine Annotation Service.
*** Goal: find a specific target/goal/project that allows everybody in work on it and shows the potential but it also small enough to be managable
*** Best practices for organizing a hackathon: there is one from the Biohackathon community.

=== Day 2 ===
==== Type Specimen Initiative ====
* additional detailed notes in the Google Doc that is linked in the agenda
* Sabine: Wikidata and Research Conference in Florence in June,
** Highlight the importance of the type specimen collections, Compile a list of type cataloges in Wikidata. Multilinguality is a strong advantage here, connected to different external identifiers. 300+ already imported. Please send Sabine other examples of other published type catalogues.
* Nicky: maybe publish list also to Zetoro. Possible to do this via API.
* There is a strong focus on zoology, but there are some from botany as well.
* Also look at extra list of typifications from other publications, e.g. Wildenowia.

* There is a discussion in the wikidata community, on whether all of the type specimens should be in Wikidata. There are some in there already. Alternative would be to have a dedicated place.
* TRE would be one of the places. Type specimens from GBIF connected to their names from IPNI. The alternative approach would be to start from literature and try to find the cooresponding specimen. The TRE data model is a bit different from Wikidata. Not all institutions properly export their type records properly to GBIF, in particular via JSTOR.
* Typfied Name is suggested to DwC, but it has been long in discussion. With that it would be a lot nicer to share type data.
* Hosted Portal with a subset from GBIF of all of the specimen that claim to be types.
* Also look at the registries, e.g. for mycology, which are their precisely for that reason. Different fields have different practices: registration,
* In particular it is difficult to find lectotypes.
* There are inconsistencies with how type information should be expressed in DwC. GBIF interprets it differently.
* The TRE is a useable approach to demonstrate the data model, importing all type specimen into Wikidata could be possible.
* While it might look, like the information about types is static, there is some changes, e.g. holotypes become lectotypes. Wikidata could handle those changes, as well as contradicting information. Synchronization is still an issue, there are a lot of data changes in GBIF for type data for example.
* There could still be a use case for keeping a dedicated Wikibase for the type specimens and just interlinking it with Wikidata via links and federated queries.
* The new version of the Taxonomic Concept Standard is up for review at TDWG, this might change the way that taxon names are shared with GBIF.
* Next steps: Which other infrastructures might be interested in a type catalogue? DiSSCo or GBIF. Proof-of-Concept will be delivered in TETTRIs, so the next further steps could be build in TETTRIs Next.

==== Other Presentations ====
* Indexing of research expeditions and linking to semantic entities (Sabine)
** Proposed as a group in TDWG a couple of years ago, is now a Task Group in TDWG
** Goal: get identifiers for expeditions, historic and contemporary
** Compile basic metadata: time, participants, …
** Link to related external entities
** Possibly an extension to DwC in the future
** Identified several applicable wikidata properties
** Issues with colonial historic background, e.g. outdated country names
** Tool to visualize journeys using Wikidata and GBIF: https://www.expeditia.info/
** 24. April: TDWG Working Group Session on Research Expeditions
** Discussion:
*** RAiD Identifier: https://raid.org/ Research Activity Identifier (doesn’t have a Wikidata Property yet)
*** Is the term expedition a bit outdated? Expedition might imply trips to undiscovered or under developed regions. Should it be a more generic Research Event?
*** Could this be expressed using Latimer Core, as a virtual collection of specimens that have the expedition in common and it would allow for estimates how many

* DiSSCo Machine Annotation Services (MAS), Wouter
** [https://docs.google.com/presentation/d/1jQp0TKJhnbKCG_IHmNmQaIHOKTQIN7GAbQbsMx-The8/edit?usp=sharing Presentation]
** Annotation Motivations: Commenting, Adding, Editing, Assessing, Deleting,
** Target Types: Term, Class, Region of Interest (in images)
** Existing services can be adopted to DiSSCo Data Model using Wrappers
** MAS Service Providers need to: Create a MAS Service and test in sandbox, get code reviewed, Service Delivery Plan and SLA
** Current Test Cases: Plant Organ Detection, AI4Labels,
** Recently: MAS Hackathon, a lot of participants, 3 new services were created.
** INDEED Tool to train quality model to judge the parts of AI based Herbarium Sheet segmentation
** Limitations: Images are not hosted by DiSSCo only the links, a centralized storage would make processing a log easier.
** Quality Control is important.

* Index of Exsiccatae (Dagmar)
** http://indexs.botanischestaatssammlung.de/
** Detailed documentation at [[Storytelling with IndExs]]
** Bound series of specimen
** Work great for storytelling, e.g. towards funders
** Some where destroyed, i.e. cut apart to but them on flat paper sheets
** This could be a different use-case for Latimer Core.

==== Any Other Business ====
* Anton will send around a draft of the new charter
* Subgroups will meet and take all of the input from this meeting in consideration.

== Logistics ==
=== Hotels ===
* ACHAT Sternhotel Bonn, Markt 8, 53111 Bonn, 90€
* IntercityHotel Bonn, Quantiusstraße 22, 53115 Bonn, 100€
* Hotel Motel One, Am Hauptbahnhof 12, and Berliner Freiheit 36, 53111 Bonn, 100€
* Hotel Kurfürstenhof, Baumschulallee 20, 53115 Bonn, 90€
* Beethoven Hotel Dreesen, Bonngasse 17, Zentrum, 53111 Bonn, 90€
* My Südstadt Bonn, Kaiserstraße 221, 53113 Bonn, 90€> (very close to Museum Koenig, but rooms are very noisy towards Kaiserstraße)
* For those who like it unusual: BaseCamp Hostel Bonn, In d. Raste 1, 53129 Bonn, 70€

Hotels on a map: https://maps.app.goo.gl/c6P5W2taKKTZD8HJ6

2025 Spring Meeting

2025-04-29T10:58:04Z

D.Fichtmüller:

= CETAF Information Science & Technology Commission - Spring 2025 Meeting =
'''Bonn, April 7-8 2025'''
== Venue ==
Leibniz Institute for the Analysis of Biodiversity Change 
Museum Koenig 
Raiffeisenhaus 
Adenauerallee 127 
53113 Bonn, Germany
(First floor, on the right. Please follow the signs!)

== Participants ==
* Anton Güntsch (FUB-BGBM, DE)
* Dominik Röpert (FUB-BGBM, DE)
* David Fichtmüller (FUB-BGBM, DE)
* Quentin Groom (Meise Botanic Garden, BE)
* Mathias Dillen (Meise Botanic Garden, BE)
* Maarten Trekels (Meise Botanic Garden, BE)
* Jiri Frank (NM, CZ)
* Adam Cironis (NM, CZ)
* Wouter Addink (Naturalis, NL)
* Dagmar Triebel (SNSB, DE)
* Stefan Seifert (SNSB, DE)
* Sabine von Mering (MfN, DE)
* Caitlin Thorn (MfN, DE)
* <s>Jonas Grieb (SGN, DE)</s>
* Claus Weiland (SGN, DE)
* <s>Anke Penzlin (SGN, DE)</s>
* André De Mûelenaere (Africamuseum, BE)
* Franck Theeten (Africamuseum, BE)
* Björn Quast (LIB, Bonn, DE)
* Birgit Rach (LIB, Bonn, DE)
* Cristina Garilao (LIB, Hamburg, DE)
* <s>Laura Tilley (CETAF, BE)</s>
* Ana Casino (CETAF, BE)
* Glorioso Alessio (CETAF, BE)
* Nicky Nicolson (Kew, UK)
* Arianna Salili-James (NHM, UK)
* Theary Ung (MNHN, Paris, FR)
* Laurent Gohy (ULiège, BE) - first day

== Agenda ==
{| class="wikitable"
!colspan="2" | ------------------------------------------------------------ Day 1 - April 7 ------------------------------------------------------------
|-
| '''12:00 - 13:00''' || '''Arrival and lunch'''
|-
| 13:00 - 13:30 || Welcome, introduction of participants, agenda, logistics
|-
| 13:30 - 14:00 || The new ISTC Wiki and future ISTC documentation
|-
| 14:00 - 15:15 || CMS Subgroup - Introduction of the new subgroup - Presentations of CMS-related activities in CETAF collections * [https://istc.cetaf.org/images/1/15/01_theeten_presentation_isct_2025.pdf Frank Theeten] * [https://docs.google.com/presentation/d/1f_mICa50WKusn94CXW0IhELABTsx4IkV/edit?usp=sharing&ouid=114384447688591455468&rtpof=true&sd=true/ Maarten Trekels] * [https://istc.cetaf.org/File:03_Seifert-ISTC-2025-04-07.pdf Stefan Seifert] * <s>Jonas Grieb</s> * [https://istc.cetaf.org/images/8/89/2025-04-07_JACQ_ISTC_Bonn.pdf Dominik Röpert] - Discussion of possible activities of the CMS subgroup and structuring of the collaboration
|-
| '''15:15 - 15:45''' || '''Coffee break'''
|-
| 15:45 - 17:00 || [https://docs.google.com/presentation/d/1UdHPtT6nYadYRgZjgOPMgDlTksrdO-CrbhMgFswh2YM/edit?usp=sharing/ AI, Robotics and Digital Collections Subgroup] - Introduction of the new subgroup - Examples of currently ongoing initiatives - Discussion of possible activities of the AI subgroup and structuring of the collaboration
|-
| 17:00 - 17:30 || Cancelled: <s>Establishment of a new Center for Knowledge Literacy and Biodiversity Informatics at the LIB (Peter Grobe)</s>
|-
| '''17:30''' || '''End of day one'''
|-
| ''19:00 -'' || ''Dinner at Tuscolo, [https://www.openstreetmap.org/?mlat=50.73294&mlon=7.09964#map=16/50.73294/7.09964 Gerhard-von-Are-Straße 8], 53111 Bonn (self paid)''
|}

{| class="wikitable"
!colspan="2" | ------------------------------------------------------------ Day 2 - April 8 ------------------------------------------------------------
|-
| 9:00 - 10:00 || [https://docs.google.com/document/d/1gnCnZgJml1dKllMoK62A8l5x93Hpmbse9Cd80TVzl98/ Type specimen initiative]
|-
| 10:00 - 11:00 || Guided tour
|-
| '''11:00 - 11:20''' || '''Coffee break'''
|-
| 11:20 - 12:20 || Misc presentations (projects, initiatives, ideas, ...): - Indexing of research expeditions and linking to semantic entities (Sabine von Mering) - Cancelled: <s>Enhancing geological specimen data (Laura Tilley)</s> - [https://docs.google.com/presentation/d/1jQp0TKJhnbKCG_IHmNmQaIHOKTQIN7GAbQbsMx-The8/edit?usp=sharing Update on MAS development in DiSSCo] (Wouter Addink) - Exsiccata series in botanical and mycological collections: [[Storytelling with IndExs|Storytelling]] with [http://indexs.botanischestaatssammlung.de/ IndExs], demo (Dagmar Triebel)
|-
| 12:20 - 12:45 || [https://docs.google.com/presentation/d/1Y4VsXEjCGDRzL7_fEMRYpqcgiD-9WUey/edit?slide=id.p2#slide=id.p2 Funding opportunities]
|-
| 12:45 - 13:00 || AOB
|-
| '''13:00''' || '''End of meeting (and packet lunch)'''
|}
== Minutes ==
=== Day 1 ===
==== The new ISTC Wiki and future ISTC documentation ====
==== CMS Subgroup ====
* Presentations are linked in the agenda
* Question to Maarten: Can the tender for their new system be published? Answer: Tender contains some confidential data, but once this has been cleared, it can be shared.
==== AI, Robotics and Digital Collections Subgroup ====
* Presentation is linked in the agenda
* Presentation by Maarten:
** DiSSCo Flanders: second phase with a stronger emphasis on specimen enrichment
** Some work done at University Ghent
** Common steps: straightening, segmenting, multi plant detection, Label OCR, Leaf extraction, identifications for specimen without any (or only rough)
** Future ideas: morphological feature extraction
* Laurent (digitization manager at University Liege): Automating Herbarium Sheet Data Extraction with AI
** specimen QR-Code photographed with camera
** directly read label information with Google Lens
** separate the labels in fields in next step
* Arianna: AI at the [Natural History] Museum [UK]
** topics AI for Digitization / collection
*** Use Cases: General Knowledge Base, based on all information in the collection, trait recognition, insect digitization,
*** Robotic Arm for pinned objects: scan drawer, recognize pins, select pin for handling, move it to photography station, take images of insect from multiple angles and label
** NHM AI Lab (also for general science questions),
*** E.g. Classifications for animal hair or diatoms,
*** Outreach via AI Coffee Lab or Hybrid Lunches, collaboration with the Turing Institute and UCL
** DCMS x NHM AI Pilot program (UK Department for Culture, Media and Sport)
*** People could propose projects, 5 selected.
*** Topics: herbarium: chat bot that answers from the perspective of a known collector
*** Segmentation and part
*** Data extraction based on old index cards
*** AI Alt text Generation
*** Predict species of reptiles based on confiscated fashion products: is the product illegal or not
* General Discussion/Next Steps (sorted by the questions suggested by Arianna)
** What is currently going on, in your institutions?
** What are hurdles to AI techniques?
*** Questionable moralities of the companies behind the LLMs (Copyright?)
*** Power consumption
*** Local or OpenSource LLMs as an alternative?
** How can robotics benefit digital collections?
** How can CETAF facilitate this better?
*** Big wins come from scaling it up to millions of specimen instead of just a couple of ones.
*** Run tools on all of CETAF collections, e.g. search for the signature of a collector
*** DiSSCo Machine Annotation service could help to move the data out of silos
*** This group could help with comparison of the different approaches, quality checks. This could be done on a benchmark subset, but will require a lot of work for a high quality ground truth. Can the creation of this dataset be automated?
*** Maybe additional funding as a COST action? Relevance?
*** Infrastructure requirements: who does this
*** Use Case: Structure unstructured data, could be relevant for the GBIF Capacity Enhancement Program, WFO and PlantNet have a similar approach.
** Mode on which the working group will operate
*** Many colleagues are working on it, but not in particular projects, general interest to continue.
*** How to keep in touch. Slack channel? Free channels will lose old posts.
*** Google Spreadsheet to have an overview who is working on what.
*** Github group
*** DiSSCo will have Hackathons for the Machine Annotation Service.
*** Goal: find a specific target/goal/project that allows everybody in work on it and shows the potential but it also small enough to be managable
*** Best practices for organizing a hackathon: there is one from the Biohackathon community.

=== Day 2 ===
==== Type Specimen Initiative ====
* additional detailed notes in the Google Doc that is linked in the agenda
* Sabine: Wikidata and Research Conference in Florence in June,
** Highlight the importance of the type specimen collections, Compile a list of type cataloges in Wikidata. Multilinguality is a strong advantage here, connected to different external identifiers. 300+ already imported. Please send Sabine other examples of other published type catalogues.
* Nicky: maybe publish list also to Zetoro. Possible to do this via API.
* There is a strong focus on zoology, but there are some from botany as well.
* Also look at extra list of typifications from other publications, e.g. Wildenowia.

* There is a discussion in the wikidata community, on whether all of the type specimens should be in Wikidata. There are some in there already. Alternative would be to have a dedicated place.
* TRE would be one of the places. Type specimens from GBIF connected to their names from IPNI. The alternative approach would be to start from literature and try to find the cooresponding specimen. The TRE data model is a bit different from Wikidata. Not all institutions properly export their type records properly to GBIF, in particular via JSTOR.
* Typfied Name is suggested to DwC, but it has been long in discussion. With that it would be a lot nicer to share type data.
* Hosted Portal with a subset from GBIF of all of the specimen that claim to be types.
* Also look at the registries, e.g. for mycology, which are their precisely for that reason. Different fields have different practices: registration,
* In particular it is difficult to find lectotypes.
* There are inconsistencies with how type information should be expressed in DwC. GBIF interprets it differently.
* The TRE is a useable approach to demonstrate the data model, importing all type specimen into Wikidata could be possible.
* While it might look, like the information about types is static, there is some changes, e.g. holotypes become lectotypes. Wikidata could handle those changes, as well as contradicting information. Synchronization is still an issue, there are a lot of data changes in GBIF for type data for example.
* There could still be a use case for keeping a dedicated Wikibase for the type specimens and just interlinking it with Wikidata via links and federated queries.
* The new version of the Taxonomic Concept Standard is up for review at TDWG, this might change the way that taxon names are shared with GBIF.
* Next steps: Which other infrastructures might be interested in a type catalogue? DiSSCo or GBIF. Proof-of-Concept will be delivered in TETTRIs, so the next further steps could be build in TETTRIs Next.

==== Other Presentations ====
* Indexing of research expeditions and linking to semantic entities (Sabine)
** Proposed as a group in TDWG a couple of years ago, is now a Task Group in TDWG
** Goal: get identifiers for expeditions, historic and contemporary
** Compile basic metadata: time, participants, …
** Link to related external entities
** Possibly an extension to DwC in the future
** Identified several applicable wikidata properties
** Issues with colonial historic background, e.g. outdated country names
** Tool to visualize journeys using Wikidata and GBIF: https://www.expeditia.info/
** 24. April: TDWG Working Group Session on Research Expeditions
** Discussion:
*** RAiD Identifier: https://raid.org/ Research Activity Identifier (doesn’t have a Wikidata Property yet)
*** Is the term expedition a bit outdated? Expedition might imply trips to undiscovered or under developed regions. Should it be a more generic Research Event?
*** Could this be expressed using Latimer Core, as a virtual collection of specimens that have the expedition in common and it would allow for estimates how many

* DiSSCo Machine Annotation Services (MAS), Wouter
** [https://docs.google.com/presentation/d/1jQp0TKJhnbKCG_IHmNmQaIHOKTQIN7GAbQbsMx-The8/edit?usp=sharing Presentation]
** Annotation Motivations: Commenting, Adding, Editing, Assessing, Deleting,
** Target Types: Term, Class, Region of Interest (in images)
** Existing services can be adopted to DiSSCo Data Model using Wrappers
** MAS Service Providers need to: Create a MAS Service and test in sandbox, get code reviewed, Service Delivery Plan and SLA
** Current Test Cases: Plant Organ Detection, AI4Labels,
** Recently: MAS Hackathon, a lot of participants, 3 new services were created.
** INDEED Tool to train quality model to judge the parts of AI based Herbarium Sheet segmentation
** Limitations: Images are not hosted by DiSSCo only the links, a centralized storage would make processing a log easier.
** Quality Control is important.

* Index of Exsiccatae (Dagmar)
** http://indexs.botanischestaatssammlung.de/
** Detailed documentation at [[Storytelling with IndExs]]
** Bound series of specimen
** Work great for storytelling, e.g. towards funders
** Some where destroyed, i.e. cut apart to but them on flat paper sheets
** This could be a different use-case for Latimer Core.

==== Any Other Business ====
* Anton will send around a draft of the new charter
* Subgroups will meet and take all of the input from this meeting in consideration.

== Logistics ==
=== Hotels ===
* ACHAT Sternhotel Bonn, Markt 8, 53111 Bonn, 90€
* IntercityHotel Bonn, Quantiusstraße 22, 53115 Bonn, 100€
* Hotel Motel One, Am Hauptbahnhof 12, and Berliner Freiheit 36, 53111 Bonn, 100€
* Hotel Kurfürstenhof, Baumschulallee 20, 53115 Bonn, 90€
* Beethoven Hotel Dreesen, Bonngasse 17, Zentrum, 53111 Bonn, 90€
* My Südstadt Bonn, Kaiserstraße 221, 53113 Bonn, 90€> (very close to Museum Koenig, but rooms are very noisy towards Kaiserstraße)
* For those who like it unusual: BaseCamp Hostel Bonn, In d. Raste 1, 53129 Bonn, 70€

Hotels on a map: https://maps.app.goo.gl/c6P5W2taKKTZD8HJ6

2025 Spring Meeting

2025-04-29T10:05:22Z

D.Fichtmüller: Minutes (part 1)

= CETAF Information Science & Technology Commission - Spring 2025 Meeting =
'''Bonn, April 7-8 2025'''
== Venue ==
Leibniz Institute for the Analysis of Biodiversity Change 
Museum Koenig 
Raiffeisenhaus 
Adenauerallee 127 
53113 Bonn, Germany
(First floor, on the right. Please follow the signs!)

== Participants ==
* Anton Güntsch (FUB-BGBM, DE)
* Dominik Röpert (FUB-BGBM, DE)
* David Fichtmüller (FUB-BGBM, DE)
* Quentin Groom (Meise Botanic Garden, BE)
* Mathias Dillen (Meise Botanic Garden, BE)
* Maarten Trekels (Meise Botanic Garden, BE)
* Jiri Frank (NM, CZ)
* Adam Cironis (NM, CZ)
* Wouter Addink (Naturalis, NL)
* Dagmar Triebel (SNSB, DE)
* Stefan Seifert (SNSB, DE)
* Sabine von Mering (MfN, DE)
* Caitlin Thorn (MfN, DE)
* <s>Jonas Grieb (SGN, DE)</s>
* Claus Weiland (SGN, DE)
* <s>Anke Penzlin (SGN, DE)</s>
* André De Mûelenaere (Africamuseum, BE)
* Franck Theeten (Africamuseum, BE)
* Björn Quast (LIB, Bonn, DE)
* Birgit Rach (LIB, Bonn, DE)
* Cristina Garilao (LIB, Hamburg, DE)
* <s>Laura Tilley (CETAF, BE)</s>
* Ana Casino (CETAF, BE)
* Glorioso Alessio (CETAF, BE)
* Nicky Nicolson (Kew, UK)
* Arianna Salili-James (NHM, UK)
* Theary Ung (MNHN, Paris, FR)
* Laurent Gohy (ULiège, BE) - first day

== Agenda ==
{| class="wikitable"
!colspan="2" | ------------------------------------------------------------ Day 1 - April 7 ------------------------------------------------------------
|-
| '''12:00 - 13:00''' || '''Arrival and lunch'''
|-
| 13:00 - 13:30 || Welcome, introduction of participants, agenda, logistics
|-
| 13:30 - 14:00 || The new ISTC Wiki and future ISTC documentation
|-
| 14:00 - 15:15 || CMS Subgroup - Introduction of the new subgroup - Presentations of CMS-related activities in CETAF collections * [https://istc.cetaf.org/images/1/15/01_theeten_presentation_isct_2025.pdf Frank Theeten] * [https://docs.google.com/presentation/d/1f_mICa50WKusn94CXW0IhELABTsx4IkV/edit?usp=sharing&ouid=114384447688591455468&rtpof=true&sd=true/ Maarten Trekels] * [https://istc.cetaf.org/File:03_Seifert-ISTC-2025-04-07.pdf Stefan Seifert] * <s>Jonas Grieb</s> * [https://istc.cetaf.org/images/8/89/2025-04-07_JACQ_ISTC_Bonn.pdf Dominik Röpert] - Discussion of possible activities of the CMS subgroup and structuring of the collaboration
|-
| '''15:15 - 15:45''' || '''Coffee break'''
|-
| 15:45 - 17:00 || [https://docs.google.com/presentation/d/1UdHPtT6nYadYRgZjgOPMgDlTksrdO-CrbhMgFswh2YM/edit?usp=sharing/ AI, Robotics and Digital Collections Subgroup] - Introduction of the new subgroup - Examples of currently ongoing initiatives - Discussion of possible activities of the AI subgroup and structuring of the collaboration
|-
| 17:00 - 17:30 || Cancelled: <s>Establishment of a new Center for Knowledge Literacy and Biodiversity Informatics at the LIB (Peter Grobe)</s>
|-
| '''17:30''' || '''End of day one'''
|-
| ''19:00 -'' || ''Dinner at Tuscolo, [https://www.openstreetmap.org/?mlat=50.73294&mlon=7.09964#map=16/50.73294/7.09964 Gerhard-von-Are-Straße 8], 53111 Bonn (self paid)''
|}

{| class="wikitable"
!colspan="2" | ------------------------------------------------------------ Day 2 - April 8 ------------------------------------------------------------
|-
| 9:00 - 10:00 || [https://docs.google.com/document/d/1gnCnZgJml1dKllMoK62A8l5x93Hpmbse9Cd80TVzl98/ Type specimen initiative]
|-
| 10:00 - 11:00 || Guided tour
|-
| '''11:00 - 11:20''' || '''Coffee break'''
|-
| 11:20 - 12:20 || Misc presentations (projects, initiatives, ideas, ...): - Indexing of research expeditions and linking to semantic entities (Sabine von Mering) - Cancelled: <s>Enhancing geological specimen data (Laura Tilley)</s> - [https://docs.google.com/presentation/d/1jQp0TKJhnbKCG_IHmNmQaIHOKTQIN7GAbQbsMx-The8/edit?usp=sharing Update on MAS development in DiSSCo] (Wouter Addink) - Exsiccata series in botanical and mycological collections: [[Storytelling with IndExs|Storytelling]] with [http://indexs.botanischestaatssammlung.de/ IndExs], demo (Dagmar Triebel)
|-
| 12:20 - 12:45 || [https://docs.google.com/presentation/d/1Y4VsXEjCGDRzL7_fEMRYpqcgiD-9WUey/edit?slide=id.p2#slide=id.p2 Funding opportunities]
|-
| 12:45 - 13:00 || AOB
|-
| '''13:00''' || '''End of meeting (and packet lunch)'''
|}
== Minutes ==
=== Day 1 ===
==== The new ISTC Wiki and future ISTC documentation ====
==== CMS Subgroup ====
* Presentations are linked in the agenda
* Question to Maarten: Can the tender for their new system be published? Answer: Tender contains some confidential data, but once this has been cleared, it can be shared.
==== AI, Robotics and Digital Collections Subgroup ====
* Presentation is linked in the agenda
* Presentation by Maarten:
** DiSSCo Flanders: second phase with a stronger emphasis on specimen enrichment
** Some work done at University Ghent
** Common steps: straightening, segmenting, multi plant detection, Label OCR, Leaf extraction, identifications for specimen without any (or only rough)
** Future ideas: morphological feature extraction
* Laurent (digitization manager at University Liege): Automating Herbarium Sheet Data Extraction with AI
** specimen QR-Code photographed with camera
** directly read label information with Google Lens
** separate the labels in fields in next step
* Arianna: AI at the [Natural History] Museum [UK]
** topics AI for Digitization / collection
*** Use Cases: General Knowledge Base, based on all information in the collection, trait recognition, insect digitization,
*** Robotic Arm for pinned objects: scan drawer, recognize pins, select pin for handling, move it to photography station, take images of insect from multiple angles and label
** NHM AI Lab (also for general science questions),
*** E.g. Classifications for animal hair or diatoms,
*** Outreach via AI Coffee Lab or Hybrid Lunches, collaboration with the Turing Institute and UCL
** DCMS x NHM AI Pilot program (UK Department for Culture, Media and Sport)
*** People could propose projects, 5 selected.
*** Topics: herbarium: chat bot that answers from the perspective of a known collector
*** Segmentation and part
*** Data extraction based on old index cards
*** AI Alt text Generation
*** Predict species of reptiles based on confiscated fashion products: is the product illegal or not
* General Discussion/Next Steps (sorted by the questions suggested by Arianna)
** What is currently going on, in your institutions?
** What are hurdles to AI techniques?
*** Questionable moralities of the companies behind the LLMs (Copyright?)
*** Power consumption
*** Local or OpenSource LLMs as an alternative?
** How can robotics benefit digital collections?
** How can CETAF facilitate this better?
*** Big wins come from scaling it up to millions of specimen instead of just a couple of ones.
*** Run tools on all of CETAF collections, e.g. search for the signature of a collector
*** DiSSCo Machine Annotation service could help to move the data out of silos
*** This group could help with comparison of the different approaches, quality checks. This could be done on a benchmark subset, but will require a lot of work for a high quality ground truth. Can the creation of this dataset be automated?
*** Maybe additional funding as a COST action? Relevance?
*** Infrastructure requirements: who does this
*** Use Case: Structure unstructured data, could be relevant for the GBIF Capacity Enhancement Program, WFO and PlantNet have a similar approach.
** Mode on which the working group will operate
*** Many colleagues are working on it, but not in particular projects, general interest to continue.
*** How to keep in touch. Slack channel? Free channels will lose old posts.
*** Google Spreadsheet to have an overview who is working on what.
*** Github group
*** DiSSCo will have Hackathons for the Machine Annotation Service.
*** Goal: find a specific target/goal/project that allows everybody in work on it and shows the potential but it also small enough to be managable
*** Best practices for organizing a hackathon: there is one from the Biohackathon community.

=== Day 2 ===
==== Type Specimen Initiative ====
* additional detailed notes in the Google Doc that is linked in the agenda
* Sabine: Wikidata and Research Conference in Florence in June,
** Highlight the importance of the type specimen collections, Compile a list of type cataloges in Wikidata. Multilinguality is a strong advantage here, connected to different external identifiers. 300+ already imported. Please send Sabine other examples of other published type catalogues.
* Nicky: maybe publish list also to Zetoro. Possible to do this via API.
* There is a strong focus on zoology, but there are some from botany as well.
* Also look at extra list of typifications from other publications, e.g. Wildenowia.

* There is a discussion in the wikidata community, on whether all of the type specimens should be in Wikidata. There are some in there already. Alternative would be to have a dedicated place.
* TRE would be one of the places. Type specimens from GBIF connected to their names from IPNI. The alternative approach would be to start from literature and try to find the cooresponding specimen. The TRE data model is a bit different from Wikidata. Not all institutions properly export their type records properly to GBIF, in particular via JSTOR.
* Typfied Name is suggested to DwC, but it has been long in discussion. With that it would be a lot nicer to share type data.
* Hosted Portal with a subset from GBIF of all of the specimen that claim to be types.
* Also look at the registries, e.g. for mycology, which are their precisely for that reason. Different fields have different practices: registration,
* In particular it is difficult to find lectotypes.
* There are inconsistencies with how type information should be expressed in DwC. GBIF interprets it differently.
* The TRE is a useable approach to demonstrate the data model, importing all type specimen into Wikidata could be possible.
* While it might look, like the information about types is static, there is some changes, e.g. holotypes become lectotypes. Wikidata could handle those changes, as well as contradicting information. Synchronization is still an issue, there are a lot of data changes in GBIF for type data for example.
* There could still be a use case for keeping a dedicated Wikibase for the type specimens and just interlinking it with Wikidata via links and federated queries.
* The new version of the Taxonomic Concept Standard is up for review at TDWG, this might change the way that taxon names are shared with GBIF.
* Next steps: Which other infrastructures might be interested in a type catalogue? DiSSCo or GBIF. Proof-of-Concept will be delivered in TETTRIs, so the next further steps could be build in TETTRIs Next.

==== Other Presentations ====
* Indexing of research expeditions and linking to semantic entities (Sabine)
** Proposed as a group in TDWG a couple of years ago, is now a Task Group in TDWG
** Goal: get identifiers for expeditions, historic and contemporary
** Compile basic metadata: time, participants, …
** Link to related external entities
** Possibly an extension to DwC in the future
** Identified several applicable wikidata properties
** Issues with colonial historic background, e.g. outdated country names
** Tool to visualize journeys using Wikidata and GBIF: https://www.expeditia.info/
** 24. April: TDWG Working Group Session on Research Expeditions
** Discussion:
*** RAiD Identifier: https://raid.org/ Research Activity Identifier (doesn’t have a Wikidata Property yet)
*** Is the term expedition a bit outdated? Expedition might imply trips to undiscovered or under developed regions. Should it be a more generic Research Event?
*** Could this be expressed using Latimer Core, as a virtual collection of specimens that have the expedition in common and it would allow for estimates how many

== Logistics ==
=== Hotels ===
* ACHAT Sternhotel Bonn, Markt 8, 53111 Bonn, 90€
* IntercityHotel Bonn, Quantiusstraße 22, 53115 Bonn, 100€
* Hotel Motel One, Am Hauptbahnhof 12, and Berliner Freiheit 36, 53111 Bonn, 100€
* Hotel Kurfürstenhof, Baumschulallee 20, 53115 Bonn, 90€
* Beethoven Hotel Dreesen, Bonngasse 17, Zentrum, 53111 Bonn, 90€
* My Südstadt Bonn, Kaiserstraße 221, 53113 Bonn, 90€> (very close to Museum Koenig, but rooms are very noisy towards Kaiserstraße)
* For those who like it unusual: BaseCamp Hostel Bonn, In d. Raste 1, 53129 Bonn, 70€

Hotels on a map: https://maps.app.goo.gl/c6P5W2taKKTZD8HJ6

2025 Spring Meeting

2025-04-07T13:11:57Z

D.Fichtmüller: formatting

2025 Spring Meeting

2025-04-07T11:14:38Z

D.Fichtmüller: added link to OpenStreetMap link for the restaurant

Main Page

2025-03-11T11:25:05Z

D.Fichtmüller: link to IIIF subpages

= CETAF Information Science & Technology Commission (ISTC) =

'''''Developing technical services for our community'''''

The Information Science & Technology Commission (ISTC) facilitates dialogue and collaboration between the IT departments of CETAF member and non-member institutions to ensure institutional interoperability through the development of common infrastructures and standards. The group works towards compatibility of components for digital information exchange and sharing, through procedural changes and adaptations to IT systems.

Members of the ISTC officially represent IT or Biodiversity Informatics departments of CETAF institutions. The group was established as a technical working group of the EU-funded project European Distributed Institute of Taxonomy (EDIT) and was integrated into CETAF in 2011.

[[Meetings]] 
[[CETAF Stable Identifier Guide|CETAF IDs]] 
[[IIIF]] 
Research Data Management 
Subgroup "Natural Science Collections and AI" 
Subgroup "Collection Management Systems"

IIIF Meise Example

2025-03-11T11:19:36Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

[[File:Screenshot_of_the_data_portal_BotanicalCollections.be_showing_one_of_the_digitized_specimens.png|thumb|Screenshot of the data portal BotanicalCollections.be showing one of the digitized specimens.]]

Meise Botanic Garden holds a herbarium with about 4 million specimens. During a first mass digitization program (DOE!) an initial set of 1.2 million specimens was imaged. Currently, a second program is expected to be finished by fall 2021 bringing the total number of specimen images to more than 2.4 million. Digital data (including the images) are provided through the data portal [http://www.botanicalcollections.be/ botanicalcollections.be]

As a result of the digitization workflow, the specimen images are available in three different formats: high quality TIFFs, JPEG2000 and lower resolution JPG. The main purpose of the high quality TIFFs is long term storage at [https://meemoo.be/en MeeMoo]. The herbarium portal is serving the JPEG2000 format.

Currently the lower resolution JPEG images are stored on a different server and are used to serve the Meise Botanic Garden herbarium dataset on GBIF. When developing the IIIF service, the least invasive option was to build a IIIF pilot based on the JPEG images.

== Implementation of the IIIF service ==

[[File:Schematic_overview_of_the_current_implementation_of_the_IIIF_service.png|thumb|Schematic overview of the current implementation of the IIIF service]]

[[File:Screenshot_the_Mirador_instance_at_Meise_Botanic_Garden._A_IIIF_image_of_a_Meise_specimen_(left)_is_displayed_next_to_a_RBGE_specimen_(right).png|thumb|Screenshot the Mirador instance at Meise Botanic Garden. A IIIF image of a Meise specimen (left) is displayed next to a RBGE specimen (right).]]

At Meise Botanic Garden, version 2.1 of the IIIF image and presentation APIs is currently implemented. The pilot is based on an existing server which contains the (lower resolution) JPEG images. This has implications on the choice of the image server, since most servers don’t support the use of JPEGs as an input format. In order to overcome this limitation, the choice was made to use the Loris image server. This is a python-based implementation that performs the tiling of the images on the fly. This made it easier to build upon existing infrastructure. However, there is a potential downside, since it might require much more computational power from the server side, especially when a large amount of requests are made to the server. An example of an image can be found here:

http://iiif-image.oxalis.br.fgov.be/V/BR0/000/025/668/070/BR0000025668070V.jpg/full/full/0/default.jpg

In order to generate the manifests, a python implementation is used as well (Code [https://github.com/iiif-prezi/iiif-prezi available on GitHub]). Currently, the design is relatively straightforward and based on the unique barcode of each specimen. The barcode can be parsed and used to retrieve the URL to the image. The metadata that is transferred to the manifest is retrieved from the data portal botanicalcollections.be. Using the CETAF stable identifier (based on the barcode), it is possible to retrieve this metadata in a machine readable RDF format. An example of a manifest can be found here:

http://iiif-manifest.oxalis.br.fgov.be/specimen/BR0000025668070V/manifest

For demonstration purposes, a Mirador instance was installed on the same server and is available here:

http://oxalis.br.fgov.be/mirador/

== Future development ==

Since the support of the Loris image server is stopping at version 2.1 of the image API, we need to adjust the architecture of the current implementation in order to move to the latest version of the IIIF APIs and since we need to redesign our IIIF service, the plan is also to check whether we can build the IIIF service on our JPEG2000 images and serve the data portal with IIIF compliant images.

Back to [[IIIF|IIIF Home]]

IIIF MfN Example

2025-03-11T11:19:24Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

[[File:Screenshot_of_the_Data_Portal_showing_a_drawing_by_Christian_Gottfried_Ehrenberg.png|thumb|Screenshot of the Data Portal showing a drawing by Christian Gottfried Ehrenberg]]

With the implementation of the Zukunftsplan, the collection of the Museum für Naturkunde Berlin with more than 30 million objects is being sustainably opened up as an international research infrastructure. The goal is to build an open, digital-analogue and internationally available collection infrastructure. The recently launched Data Portal is part of this process and promotes knowledge-based debates about the future of society and the relationship between humans and nature. At the time of its first release in early 2021, the [https://portal.museumfuernaturkunde.berlin/ Data Portal] already contains over 40,000 entries from three different sub-collections, which are now publicly accessible and usable for everyone interested.

== Implemenation ==

To offer the best user experience all images are delivered through IIIF. Thus allowing users to smoothly zoom in and zoom out high-resolution images even when only a limited download bandwidth is available.

We use a range of technologies to offer IIIF integration. These include 3rd party tools and libraries as well as self-developed utilities. For example, all tiles are pre-generated with libvips. For the frontend, we use the well-known OpenSeadragon library and customized IIIF viewers, namely Mirador.

== Future development ==

In the future, we plan to reimplement our IIIF server to improve maintainability and to allow for better integration of upcoming technologies such as JPEG XL. Also, we will continue our contribution to community-driven projects such as Mirador or Tify.

Back to [[IIIF|IIIF Home]]

IIIF BGBM Example

2025-03-11T11:18:03Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

Since the beginning of digitisation at the BGBM in 1999, we have relied on zoomable image formats and software. The image format fpx was used for this. In the course of time, we had to use different commercial server software systems for on-the-fly provision of images, as there has been a discontinuation of software products over the last 20 years. Furthermore, there was hardly any software capable of both running in the cloud and managing extensive image inventories locally. One of the main goals here was to enable variable image display in the different resolutions needed without having to do any prior image processing.

Three years ago, we started to provide all BGBM specimen images (~400,000) via an iiif server in parallel to the existing systems. The migration to iiif-only image delivery was completed in early 2020.

== Implementation ==

[[File:Screenshot_of_BGBM_Internal_image_management_system.png|thumb|Screenshot of BGBM Internal image management system]]
Currently we use the IIIF server digilib for IIIF display of our images. The use of digilib gave us the possibility to use our existing image formats (tif, jpg) directly without having to do extensive conversions, because digilib can use jpeg directly via a plugin. The diglib server is integrated into our internal image management system as a publication server.

In our portals we use the Mirador 2 viewer and the OpenSeadragon viewer. At the moment, all our IIIF outputs are implemented in APIs version 2.1. The creation of the manifest files is done in the context of content negotiation when requesting the corresponding endpoint. The underlying services and functions have been developed using the [https://www.slimframework.com/ SLIM PHP] framework based on scripts developed at the RBGE Edinburgh ([https://git.bgbm.org/cetaf/stableidentifiernegotiation Code available in GitLab]).

We have recently started publishing the manifest file via our BioCASe Provider Software installations (see section Linking with ABCD Metadata) and we are testing the presentation in external portals such as GBIF and Europeana. The individual fields in the manifest file correspond to dwc fields and are filled on-the-fly from JACQ. We are offering this functionality to other herbaria that also manage their specimen data in JACQ as a service for making their associated images available via IIIF.

== Future development ==

As next steps we want to make further image sources (autographs, living specimens, archivals) available via IIIF services. We also plan to implement access to our IIIF elements via searches by name or person similar to the capabilities developed in Edinburgh.

The implementation of version 3 of the IIIF API is also under way.

Back to [[IIIF|IIIF Home]]

IIIF Herbaria Mundi

2025-03-11T11:16:22Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

As mentioned above, one of the key things that botanists do is to compare herbarium specimens within and between herbaria. From the researchers perspective it would be ideal if all the specimens existed in a single herbarium, the one they were in. IIIF should allow this to happen, at least virtually, and [https://www.herbariamundi.org/ Herbaria Mundi] (World Herbarium) was set up as a demonstration of what such a system might look like.

== Implementation ==
[[File:Search_page_within_Herbaria_Mundi.png|thumb|Search page within Herbaria Mundi]]
[[File:Popup_window_in_Herbaria_Mundi_pulling_zoom_data_from_the_specimen%E2%80%99s_institution.png|thumb|Popup window in Herbaria Mundi pulling zoom data from the specimen’s institution.]]

The system consists of an Apache Solr index of six hundred thousand specimens from RBGE and BGBM as well as a few stored in Zenodo. The index was built by polling the CETAF IDs for each specimen, indexing the associated specimen data and generating a thumbnail image from the IIIF end point for the specimen. Only specimens with associated IIIF Manifests were included in the index.

Users can log into the system using their ORCID IDs. They can then search and browse the specimens as if this were a catalogue of a single herbarium (Figure 13). Tools allow the specimens to be tagged and determined to species according to the current World Flora Online taxonomy and to compare sets of specimens side by side. The higher resolution images for zoom are all called live from the host institutions.

An issue that researchers face using such a system is incorporating specimens that are not available through CETAF IDs and IIIF. This may be because the specimens were only collected for identification purposes and will never enter a herbarium or have not been digitised yet. A demonstration was created where specimen images can be uploaded to the [https://zenodo.org/communities/herbariamundi Zenodo repository] and then presented through a caching server to Herbaria Mundi.

== Future development ==

By the end of Task 4.3 Herbaria Mundi was acting as a good demonstration of how a single global herbarium might work (it was presented at [https://biss.pensoft.net/article/59055/ TDWG 2020 conference]) but it wasn’t a complete production system. Going forward a number of design changes are required. At the start of the project IIIF Manifest URIs were not being indexed by GBIF but they are now. There is therefore no longer a need for Herbaria Mundi to build its own index, a task that is very resource intensive. It should be able to interact with the GBIF API to find specimens with associated IIIF Manifests. The Mirador viewer version 3 is now stable and the annotation plugin is being actively developed by the wider community. More features could be made available more quickly by switching to this viewer. It is planned to continue developing Herbaria Mundi along these lines.

Back to [[IIIF|IIIF Home]]

IIIF RBGE Example

2025-03-11T11:13:45Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

= Herbarium =

The RBGE Herbarium contains approximately three million specimens. An [https://data.rbge.org.uk/search/herbarium/ online herbarium catalogue] presents metadata on around one million of these and zoomable, high resolution images of about half of those. The specimen images are the result of a complex internal process that has developed over the last decade. The final stage of the process is to build an image tile pyramid of the specimen and store it in a ZIP file. A bespoke web service then exposes this data as [http://www.zoomify.com/ Zoomify] end point.

[[File:Digitisation_workflow_at_RBGE.png|thumb|Digitisation workflow at RBGE]]

The system works well and the online catalogue is used both within the organisation and by researchers from around the world. There was no need to make changes to the overall process however there were two areas that made adoption of IIIF desirable. Firstly the Zoomify endpoint restricts the choice of viewers in the catalogue. Secondly, because other herbaria do not use Zoomify in the same way, opportunities for interoperability were restricted.

== Implementation ==

We therefore built our IIIF implementation as a wrapper around our existing infrastructure (Figure 11). A relatively simple set of bespoke PHP scripts ([https://github.com/rogerhyam/iiif_rbge_herb available in GitHub]) implement the Image and Presentation APIs by calling the collections metadata in an Apache Solr index (the same one that feeds the catalogue) and the existing Zoomify API for images.

[[File:Data_flow_through_PHP_wrapper_to_serve_IIIF_at_RBGE.png|thumb|Data flow through PHP wrapper to serve IIIF at RBGE]]

Once the IIIF service was in place and proved to be stable the existing Zoomify viewer in the catalogue was swapped out for an OpenSeadragon viewer that calls the IIIF Image API. This means the catalogue and backend are further decoupled and we could switch either out in the future if that became desirable.

Having implemented the IIIF service we were able to add the manifest URIs to our Darwin Core Archive feed to GBIF using the mechanism described in the section above. This means our specimens are displayed in the GBIF data portal with draggable IIIF icons along with those from other collections. The manifests are also available through the GBIF API for incorporation into other applications.

== Future development ==

Looking to the future we may be able to include OCR and Citizen Science data gathered about specimens as IIIF annotations. We also hope our specimens will be exploited in IIIF based taxonomic work benches.

= Padme =

The RBGE herbarium catalogue is strictly limited to storing data relating to specimens stored in Edinburgh, as such it has a significantly more limited scope than Padme. Nevertheless, specimens collected by Edinburgh researchers will be stored in the RBGE herbarium, digitally imaged to a very high resolution, and recorded in the catalogue. It is therefore of significant advantage for researchers within Padme to be able to view the high-resolution specimen images alongside any images relating to that specimen stored in Padme. For example, it is common for RBGE staff to construct a montage of images documenting the specimen as it was found in the field and store them in Padme as well as the image of the dried voucher specimen taken by the herbarium.

== Motivation for the Padme IIIF Image API implementation ==

Both the herbarium images and the images stored in Padme are available as Zoomify stacks. However, the APIs used to access those stacks were independently developed and somewhat different in character. IIIF offered a way to unify the APIs used to access images stored directly in Padme and those available via the Herbarium catalogue thus significantly simplifying the coding required to support viewing of the images.

Padme uses the OpenSeadragon viewer to display the zoomable images of objects stored in its datasets. Initially the OpenSeadragon configuration in Padme utilised the IIIF API for displaying the Herbarium images and the native zoomify tile stack viewing ability of the viewer to display the images stored directly in Padme. By implementing an IIIF image API endpoint as a wrapper around the existing Padme Zoomfiy stacks, images from both sources can be viewed simply by supplying a correctly formed URI to the viewer so that it can obtain the necessary info.json file.

Although it would only have been necessary to implement the IIIF Image API to achieve this goal, the concomitant advantages in terms of unified image sharing also made it worthwhile implementing a Padme specific IIIF Presentation API endpoint.

== Padme IIIF Image API implementation ==

The implementation of the wrapper around the zoomify stacks was realised as a single PHP script and relatively straightforward to implement. Implementing the endpoint as a wrapper meant that all the existing code written to manage and build the stacks could be left unchanged. The only tricky part being the implementation of the logic required to recognise when a tile was being requested rather than an arbitrary region of the image. There is no mechanism in the IIIF URI scheme for explicitly requesting a tile. The current Padme IIIF Image API implementation is complete except that upscaling of image regions is not supported. Including implementation and testing, two working days were required to complete the work.

== Padme IIIF Presentation API ==

Padme exposes three IIIF Presentation API endpoints to satisfy the three use cases for image access so far identified. These are implemented as three layers each with a standard form of URI and representing increasing levels of abstraction . As with the image API, the endpoint was implemented as a set of PHP scripts. The hardest part of this section of the implementation was recreating the nested objects required to populate a manifest. Although not technically difficult to achieve, ensuring that the correct structure had in fact been created was not so trivial. In hindsight use of a third-party library in this respect may well have saved considerable time.

=== Layer 1: Access to a single image. ===

* https://padme.rbge.org.uk/padmeweb/iiif/%7Bimageid%7D – redirects to the manifest
* https://padme.rbge.org.uk/padmeweb/%7Bimageid%7D /manifest – returns the presentation API manifest for the image containing a single canvas for the image.
* https://padme.rbge.org.uk/padmeweb/iiif/%7Bimageid%7D/info.json - returns the Image API json file
* https://padme.rbge.org.uk/padmeweb/%7Bimageid%7D/%7Bimage/tileparams%7D – returns the pixel data from the specified region of the image as per the Image API specification.

=== Layer 2: Access to a set of images associated with an observation ===

* http://padme.rbge.org.uk/padmeweb/iiif/%7Bdatasetid%7D/observation/%7Bobservationid%7D – redirects to the manifest
* http://padme.rbge.org.uk/padmeweb/iiif/%7Bdatasetid%7D/observation/%7Bobservationid%7D/manifest – returns a Presentation API manifest with a canvas item for each image associated with an observation. Each canvas item will contain a URI of the form https://padme.rbge.org.uk/padmeweb/iiif/%7Bimageid%7D/info.json i.e. a reference back to layer 1.

=== Layer 3: Access to a set of manifests associated with a species name ===

* http://padme.rbge.org.uk/padmeweb/iiif/%7Bdatasetid%7D/species/%7Bspecies_name%7D – redirects to the manifest
* http://padme.rbge.org.uk/padmeweb/iiif/%7Bdatasetid%7D/species/%7Bspecies_name%7D/manifest – returns a presentation API collection with an item for each observation associated with the requested species name. Each item in the collection contains a URI in the form http://padme.rbge.org.uk/padmeweb/iiif/%7Bdatasetid%7D/observation/%7Bobservationid%7D/manifest, i.e. a reference back to layer 2.

'''Note:''' Padme stores images from all datasets in a single image store. However, specimen, field note, and species records are stored within separate data sets corresponding to different projects within the Padme system. Therefore, only layer one URIs can be dataset agnostic.

== Image sharing and Padme ==

[[File:Screen_shot_from_the_RBGE_Begonia_Resource_centre_displaying_field_images_of_the_collection_and_a_IIIF_drag_%27n%27_drop_link.png|thumb|Screen shot from the RBGE Begonia Resource centre displaying field images of the collection and a IIIF drag 'n' drop link.]]

Padme provides a content management system (CMS) that allows Padme users to present their data via the web (Figure 12). Within the CMS, images are presented either as part of a gallery or embedded within the results for searches on specimen data. Images displayed in the latter context include the IIIF drag ‘n’ drop logo using the Layer 2 manifest form described above thus facilitating open sharing of the images. The gallery facility is currently being rewritten and will include IIIF drag ‘n’ drop logos using the layer 1 manifest form.

== Future development ==

The image handling in Padme will shortly be updated to allow Padme to act as a drop target for IIIF drag ‘n’ drop logos allowing Padme users to store references to plant images from external sources without requiring an explicit download of the image.

Back to [[IIIF|IIIF Home]]

IIIF Linking CSV

2025-03-11T11:04:05Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

It is very common to exchange data as simple CSV files, often created or manipulated in spreadsheet programs such as Microsoft Excel. The problem with this approach is that the data in the columns isn’t typed and the column headers are not standardised. It can be difficult for humans to know what the contents of a column represents. A standard column name is therefore proposed here.

'''Recommendation:''' When exchanging specimen data in CSV files the column that contains the URI of the IIIF Manifest associated with the specimen should be called iiifManifestUri.

Back to [[IIIF|IIIF Home]]

IIIF Linking ABCD

2025-03-11T11:03:32Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

Images are provided in ABCD using the repeatable MultimediaObject node, meaning multiple objects per specimen can be provided in a single ABCD record. Thus, the IIIF manifest can be included in a similar way as for DarwinCore Archives - by adding another MultimediaObject entry equivalent to the Audubon Core extension record as in the example below.

[[File:Example_of_RDF-XML_of_ABCD_showing_inclusion_of_IIIF_Manifest_link.png|Example of RDF-XML of ABCD showing inclusion of IIIF Manifest link]]

This should allow GBIF to harvest IIIF manifests from ABCD in the same manner as for DarwinCore archives.

ABCD is also used for delivering multimedia objects to [https://www.europeana.eu/ Europeana], the European virtual library for cultural objects, by OpenUp!, the natural history aggregator. Europeana already uses IIIF to incorporate images into the data portal, and [http://open-up.eu/ Openup!] is currently testing provision of IIIF manifests in the way described above.

[[File:IIIF_in_Europeanas_data_portal_-_BGBM_specimen_provided_using_ABCD.png|IIIF in Europeanas data portal: BGBM specimen provided using ABCD]]]]

'''Caution:''' Do not assume that providing a link to a IIIF manifest has to replace existing links to JPG and other media types. IIIF can be provided alongside existing mechanisms for sharing media objects. Even in new installations it may be convenient to also publish direct links to lower resolution JPG images so as to maximise compatibility. This could be achieved by linking directly to the IIIF Image API with a URI specifying an appropriate image size.

Back to [[IIIF|IIIF Home]]

IIIF Linking Darwin Core

2025-03-11T11:02:06Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

Many institutions publish their data to GBIF and other data aggregators using the [https://dwc.tdwg.org/ Darwin Core] metadata standard and its extensions. During the course of the project we established a convention for using the [https://www.tdwg.org/standards/ac/ Audubon Core] multimedia extension to publish IIIF manifest locations through Darwin Core. The extension is used in essentially the same way as it would be for a JPEG file. The figure below shows an example of a Audubon Core extension in a Darwin Core Archive metadata file.

<pre><extension
encoding="UTF-8"
fieldsTerminatedBy=","
linesTerminatedBy="\n"
fieldsEnclosedBy="""
ignoreHeaderLines="0"
rowType="http://rs.tdwg.org/ac/terms/Multimedia">
<files>
<location>darwin_core_images.csv</location>
</files>
<coreid index="0"/>
<field index="1" term="http://purl.org/dc/elements/1.1/type"/>
<field index="2" term="http://purl.org/dc/elements/1.1/format"/>
<field index="3" term="http://rs.tdwg.org/ac/terms/accessURI"/>
<field index="4" term="http://rs.tdwg.org/ac/terms/associatedSpecimenReference"/>
<field index="5" term="http://purl.org/dc/terms/identifier"/>
<field index="6" term="http://purl.org/dc/terms/description"/>
<field index="7" term="http://ns.adobe.com/xap/1.0/rights/Owner"/>
<field index="8" term="http://purl.org/dc/terms/rights"/>
<field index="9" term="http://purl.org/dc/elements/1.1/rights"/>
<field index="10" term="http://purl.org/dc/elements/1.1/creator"/>
<field index="11" term="http://rs.tdwg.org/ac/terms/serviceExpectation"/>
</extension></pre>
In the associated CSV file (in this case darwin_core_images.csv) the columns for the manifests would contain “application/ld+json” in the third column (dc:format), the URI of the IIIF manifest in the fourth column (ac:accessURI) and “IIIF” in the twelfth column (ac:serviceExpectation).

This can be implemented using the GBIF Integrated Publishing Toolkit. All records in the Meise Botanic Garden Herbarium that have an image of the specimen (about 1.3 M images available at the time of writing) have 2 rows in the Audubon Core extension. The first row is describing the available JPEG file, the second row is including the IIIF manifest.

[[File:Screenshot_of_the_IPT_of_Meise_Botanic_Garden_with_the_usage_of_the_%E2%80%98Audubon_Media_Description%E2%80%99_extension.png|Screenshot of the IPT of Meise Botanic Garden with the usage of the ‘Audubon Media Description’ extension.]]

This technique worked successfully and GBIF has added IIIF Icons to their portal interface.

[[File:Example_of_actionable_IIIF_Icon_from_RBGE_data_in_GBIF_data_portal.png|Example of actionable IIIF Icon from RBGE data in GBIF data portal]]

'''Recommendation:''' If you publish data using Darwin Core Archive format, please add the manifest locations using this method. They will then automatically appear in the GBIF portal as interoperable links and in the GBIF data API for incorporation into other applications.

Back to [[IIIF|IIIF Home]]

IIIF Linking CETAF IDs

2025-03-11T11:00:03Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

== Linking IIIF Manifest to CETAF ID Metadata ==

The RDF metadata provided by the CETAF ID can be linked to in the same way as the catalogue page.

<pre> "seeAlso": [
...
{
"id": "https://data.rbge.org.uk/herb/E00588402#rdf",
"type": "Dataset",
"label": {
"en": [
"Specimen description in RDF XML."
]
},
"format": "application/rdf+xml"
}
],</pre>
'''Recommendation:''' If you implement CETAF IDs at Level 2 or above include a seeAlso resource in the Manifest resource for the specimen. Set the type property to “Dataset” and the format to “application/rdf+xml”. Append the anchor #rdf to the end of the URI.

'''Recommendation:''' Include an English language label for the link plus labels in as many other languages as appropriate for the collections location.

'''Caution:''' The IIIF Presentation API requires each seeAlso id to be unique but CETAF IDs use content negotiation to provide the same data in multiple formats for a single URI. It is therefore necessary to create multiple unique URIs based on the CETAF IDs to express multiple formats in IIIF. Fortunately this can be achieved simply appending an # anchor to the end of the URIs. This is safe because the CETAF URI will not already contain an anchor (the specification stipulates not to include one) and the server will ignore any anchor when the URI is resolved. Meanwhile the URIs will appear as unique to software consuming the IIIF Manifest.

== Linking CETAF ID Metadata to IIIF Manifest ==

We need a way to indicate to a machine that is ingesting CETAF ID metadata that there is a IIIF resource associated with the specimen being described. We do this by creating a typed link using the [https://www.dublincore.org/specifications/dublin-core/dcmi-terms/elements11/relation/ Dublin Core Relation] property. This conceptually is very similar to the way the IIIF manifests use the seeAlso link. We describe an RDF resource that has the id of the IIIF Manifest URI and specify that the type of this resource is a IIIF manifest and the format is JSON-LD. It is possible to include any number of application specific properties here should that be necessary. The [http://herbal.rbge.info/index.php?uri=https://data.rbge.org.uk/herb/E00421509 default example in the CETAF URI tester] has a live example of how this is done.

<pre><dc:relation>
<rdf:Description rdf:about="https://iiif.rbge.org.uk/herb/iiif/E00421509/manifest">
<dc:identifier rdf:resource="https://iiif.rbge.org.uk/herb/iiif/E00421509/manifest"/>
<dc:type rdf:resource="http://iiif.io/api/presentation/3#Manifest"/>
<dc:subject rdf:resource="https://data.rbge.org.uk/herb/E00421509"/>
<dc:format>application/ld+json</dc:format>
<dc:description xml:lang="en">A IIIF resource for this specimen.</dc:description>
</rdf:Description>
</dc:relation></pre>
[[File:RDF_Model_of_typed_link_to_IIIF_Manifest_-_larger.png|RDF Model of typed link to IIIF Manifest]]

'''Recommendation:''' If you publish RDF metadata for your specimens include a dc:relation property that describes the IIIF Manifest with the dc:type http://iiif.io/api/presentation/3#Manifest and the dc:format application/ld+json

'''Recommendation:''' Include an English language dc:description property in your rdf:Description plus dc:descriptions in as many other languages as are appropriate.

Back to [[IIIF|IIIF Home]]

IIIF Linking HTML

2025-03-11T10:58:33Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]
== Linking HTML Page to IIIF Manifest ==

Humans are most likely to consume metadata as web pages in collection catalogues. In these situations IIIF data will usually be presented using an embedded IIIF viewer such as [https://projectmirador.org/ Mirador] or [https://universalviewer.io/ Universal Viewer]. If a zoomable image is all that is required then the [https://openseadragon.github.io/ OpenSeadragon] viewer can be used on its own to present just the Image API, the metadata being presented in the rest of the catalogue page.

When viewers are used to embed resources in pages the user may not be aware that there is a IIIF resource associated with this specimen at all and therefore not aware that the image data could be used in other applications. It is therefore recommended to include a draggable IIIF icon as part of the metadata for the specimen. Clicking on the icon will open the IIIF resource in a new window or tab. Dragging the icon onto a suitable IIIF viewer adds it to that viewer. Figure 3 and Figure 4 give examples of the use of such an icons in the RBGE herbarium catalogue and JACQ systems.

[[File:Screenshot_from_RBGE_herbarium_collection_catalogue.png|Screenshot from RBGE herbarium collection catalogue]]

[[File:Screenshot_from_JACQ_system_showing_draggable_IIIF_icon.png|Screenshot from JACQ system showing draggable IIIF icon]]

From the coding perspective such icons are simple to add. An example of the HTML code used is a follows

<pre><a target="_blank" href="mirador/?manifest=https://iiif.rbge.org.uk/herb/iiif/E00008781/manifest">
<img
src="logo-iiif.png"
alt="IIIF Manifest"
title="Click to use IIIF viewer or drag'n'drop to add to open viewer"
draggable="true"
>
</a></pre>
Note that the HTTP URI in the href of the link must be a link to a viewer page that accepts the ?manifest= parameter. This means the host institution needs to provide a IIIF Viewer instance or access a publicly available instance.

'''Recommendation:''' If an institution has implemented IIIF and has an online catalogue it should include draggable IIIF icons of this form on its catalogue web pages.

== Linking IIIF Manifest to HTML Page ==

The seeAlso property in the IIIF Manifest is used to link to human readable data for the specimen. The CETAF ID makes a good link to the catalogue page for the specimen.

<pre> "seeAlso": [
{
"id": "https://data.rbge.org.uk/herb/E00588402#html",
"type": "Text",
"label": {
"en": [
"Catalogue page for this specimen."
]
},
"format": "text/html"
},
...
],</pre>
'''Recommendation:''' Include a seeAlso resource in the Manifest resource object for the specimen with the id set to the CETAF ID for the specimen. Set the type property to “Text” and the format to “text/html”. Append the anchor #html to the end of the URI.

'''Recommendation:''' Include an English language label for the link plus labels in as many other languages as appropriate for the collections location.

Back to [[IIIF|IIIF Home]]

IIIF Framework

2025-03-11T10:51:51Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF Pages]]

__TOC__
It can be daunting for a newcomer to reach an understanding of what IIIF is as it consists of a series of technical and social components working together towards three goals ([https://iiif.io/about/ from the IIIF website]):

* To give scholars an unprecedented level of uniform and rich access to image-based resources hosted anywhere.
* To define a set of common application programming interfaces that support interoperability between image repositories.
* To develop, cultivate and document shared technologies, such as image servers and web clients, that provide a world-class user experience in viewing, comparing, manipulating and annotating images.

The four components that make up IIIF in the broad sense are:

# Technical standards in the form or Application Programming Interfaces (APIs).
# Software applications including image viewers, server components and scripts that run in the background to publish image data.
# The [https://iiif.io/community/consortium/ IIIF Consortium (IIIF-C)], a membership organisation that provides steering and sustainability for the IIIF community. It comprises more than 40 Founding Members who have committed to support the growth and adoption of IIIF. It has a small paid staff and is most visible in organising workshops, conferences and training events.
# The IIIF community which includes the adopters, users and developers of IIIF standards and software. By extension, dear reader, that includes you.

Here we will mainly discuss IIIF in the narrow sense of the APIs and software but these are just the concrete manifestation of the collaboration between individuals and institutions who maintain them. There are currently six distinct APIs. Below is a brief outline of what they do and how they interact with each other. The specifications themselves are quite accessible and provide full descriptions of each API.

'''Recommendation:''' The most recent versions of the APIs are Version 3.0 for Image and Presentation and Version 1.0 for Authentication, Search and Change Discover. Adoption of these most current versions of APIs is recommended. Earlier versions are not discussed here.

= IIIF APIs - Summary =

Images are exposed to the world through a set of APIs. The '''Presentation API''' describes what the images are and how they relate to both each other and the object they are of - so a human knows what they are looking at. The '''Image API''' provides the pixels to display on the screen. The '''Search API''' makes it possible to find text within objects like books. There is an '''Authentication API''' in case you need to control who can see what and a '''Change Discovery API''' to keep track of modifications to big collections. The new kid on the block is the '''Content State API''' that enables you to direct someone to a particular place within a complex multimedia object.

But, as the Wizard Gandalf might say, ''“The one API to rule them all, the one API to find them, the one API to bring them all, and in the darkness bind them”'' is the Presentation API.

== Image API ==

The [https://iiif.io/api/image/3.0/ Image API] defines how a client application can retrieve the pixels of an image to display. It is similar to other image server APIs. Two types of call are specified. One returns a simple JSON based description of the image, such as its pixel dimensions, the other defines the syntax of a URI. This syntax can specify the region, size, rotation, quality characteristics and format of the image to be returned.

[[File:Example_from_Image_API_specification.png|404px|Example from Image API specification for a URI ending .../pct:41.6,7.5,66.6,100/max/0/default.jpg]]

One of the main uses of the Image API is to provide a tile service whereby the original image is divided into sub-images at various resolution levels. This allows the client application to zoom the image without downloading the whole file from the server.

An important feature of the Image API is the notion of [https://iiif.io/api/image/3.0/compliance/ Compliance Level]. Although a suite of image manipulation features are specified, installations can implement a subset of these features and still be compliant. Level 0 compliance can be achieved with only static files and no dedicated software at all.

[https://openseadragon.github.io/ OpenSeadragon] is a popular image viewer that can read image tile services provided by IIIF.

If IIIF only consisted of the Image API then it would not have made such a significant contribution to sharing images online. Image servers have had similar REST APIs for many years. Where IIIF goes further is in the Presentation API.

'''Recommendation:''' Because the Image API is so similar to APIs already provided by image servers it may be a good first step on the path to deploying IIIF on your collection. An existing image server may support publishing as IIIF Image API already (see the [https://iiif.io/apps-demos/#image-servers IIIF website for examples] ) or a wrapper script could be written to translate between the two (as is done for Djakota and FSI Servers)

'''Caution:''' Don’t stop here! It may be tempting to flick the switch on an image server to enable the Image API and feel the job is done but without the Presentation API in place the Image API offers few advantages over regular image servers. The minimum needed to integrate with others is to have both the Image API and the Presentation API running.

== Presentation API ==

The IIIF [https://iiif.io/api/presentation/3.0/ Presentation API] specifies how multiple images (and other media and data) relate to a real or virtual object and to each other. If we consider the case of a field notebook containing hand written observations associated with specimens in a museum. It may have many pages. The handwriting may not be legible to the unfamiliar and so providing a transcription is important. It may be desirable to provide translations to other languages and scholarly interpretation to make it useful for other researchers. The ordering of the pages and layering of annotations onto these pages isn’t possible from a simple image server but requires some way to specify the relationships between these different pieces of data. This is what the Presentation API enables. From the specification:

<blockquote>“A compound object may comprise a series of pages, surfaces, or extents of time; for example the single view of a painting, the two sides of a photograph, four cardinal views of a statue, the many pages of an edition of a newspaper or book, or the duration of an act of an opera. This specification addresses how to provide an order for these views or extents, the references to the resources needed to present them, and the descriptive information needed to allow the user to understand what is being seen or heard.”
</blockquote>
The syntax of the Presentation API is [https://json-ld.org/ JSON-LD] which combines the now ubiquitous [https://en.wikipedia.org/wiki/JSON JSON] data exchange format with [https://en.wikipedia.org/wiki/Linked_data Linked Data] principles. The result is a format that can be parsed by commonly available software libraries on all platforms and is also easy to interlink with other data. In addition to this the current version (3.0) has incorporated the [https://www.w3.org/TR/annotation-model/ W3C Web Annotation Data Model] (with some caveats around the label property) allowing for extension and integration with generic annotation servers.

The data model (Figure 2) can appear daunting at first but is easily summarised.

# Manifests represent real world objects such as specimens or books.
# Collections define sets of Manifests and other Collections.
# Canvases are views of the object such as pages, sides, angles, different times.
# Ranges order Canvases such as page order.
# Annotations represent everything else. An image from an Image API service will be attached to a canvas as an annotation of that canvas. Text notes will be layered on in the same way. Annotations are further organised into pages and collections.

See the [https://iiif.io/api/presentation/3.0/ full specification] for a more detailed explanation of the structure.

[[File:Presentation_API_Data_Model_(from_version_3.0_specification).png|329px|Presentation API Data Model (from version 3.0 specification)]]

The Presentation API offers a specific implementation challenge because the data contained in a manifest file may need to come from more than one system within an institution. The curation of image files is often delegated to a generic Digital Asset Management system (DAM) separate from the database used to curate specimens in the collection. The DAM may be capable of exposing images using the Image API but not have the information needed to populate the labels in the Presentation API, data which is stored in the collection database. Likewise the collection database may have all the information for the labels but not know the dimensions to size the canvases. The system that publishes the Presentation API to the internet must be able to pull this information from wherever it is stored in the institution and this will require collaboration between systems and the people who run them.

'''Recommendation:''' At an early stage in implementation make sure that the people responsible for the relevant systems are involved and that they have the technical skills required. Pulling the data together shouldn’t be technically challenging if the right people are involved.

'''Caution:''' Terminology can be confusing. The word manifest is used as a name for just about all Presentation API response documents. This is because usually there is one Manifest representing a single real world object in each file. But this is not always the case. A manifest file (response from the API) might contain Collections and multiple Manifests. Here Manifest (capital M) is used for the object and manifest (small m) is used in the loose sense of a IIIF Presentation API document.

== Search API ==

Some IIIF objects (Manifests, Collections and Ranges) can contain large amounts of text. IIIF representations of books and newspapers are perhaps the examples that jumps to mind for this but even simple IIIF objects may contain multiple textual annotations. An image may have been OCR’d or transcribed and this text translated or interpreted by multiple scholars. There are therefore occasions where the user may want to search within a IIIF object. The [https://iiif.io/api/search/1.0/ Search API] enables this.

'''Recommendation:''' Typical Natural History specimens have little text associated with them. Unless you have users who specifically require this functionality or are publishing manuscripts it is probably best to ignore the Search API during the initial roll out of IIIF.

== Authentication API ==

Open access to content is desirable, but internal policies, legal regulations, business models, and other constraints can require users to authenticate and be authorized to interact with some resources. In IIIF this might also include access to certain zoom levels, adding watermarks to content or other measures. The [https://iiif.io/api/auth/1.0/ IIIF Authentication API] provides a guide to integrating existing authentication/authorisation systems within the IIIF viewer experience.

'''Recommendation:''' It is unlikely that the Authentication API will be needed during initial implementations of IIIF on Natural History collections because collections tend to default to open access. An exception is the obfuscation of location data on endangered species. This is already addressed by most collections only providing access on request to these records rather than requiring authentication for their whole collection. The Authentication API may be of importance in future rounds of implementation.

== Change Discovery API ==

A [https://iiif.io/api/discovery/1.0/ Change Discovery API] service describes changes to IIIF content resources and the location of those resources to harvest. Content providers can implement this API to enable the collaborative development of global or thematic search engines and portal applications that ultimately allow users to easily find and engage with content available via existing IIIF APIs. Change Discovery API is the most recent API to become stable (Version 1.0)

'''Recommendation:''' As discussed in the introduction the Natural History community has multiple metadata standards for aggregating specimen metadata. At this stage the Change Discovery API therefore seems redundant for our needs though may form a part of future network infrastructure.

== Content State API ==

The [https://iiif.io/api/content-state/0.9/ Content State API] provides a way of describing a Presentation API resource, or a part of a resource, in a compact format that can be used to initialize the view of that resource in any client that implements this specification. It provides the format of the “content state”, and mechanisms for passing it between applications regardless of their user interfaces and capabilities.

'''Recommendation:''' The Content State API is still in Beta so it is not recommended for adoption at this point, unless it meets specific current needs.

== Three Dimensional Models ==

Discussion here is focussed on two dimensional media. This is partly due to the predominance of herbaria within the project but also the current dominance of two dimensional images across many subdomains of Natural History. It is easier to start with flat photographs of objects and so that is what has been done. As it stands the IIIF Presentation API allows multiple views of three dimensional objects to be presented and related to each other. It is possible to present, for example, the dorsal, ventral, lateral views of an insect or focus stack slices from a diatom in a single manifest to great effect. There is, however, also active development in the IIIF community to bring true 3D modelling into the standard and an official community group to steer this.

'''Recommendation:''' If you have an interest in 3D modelling on Natural History objects using IIIF it may be worth joining the [https://iiif.io/community/groups/3d/ IIIF 3D Community Group].

== Time Based Media ==

Most Natural History museum objects are static and can be represented by one or a few still images. Version 3 of the IIIF Presentation API does however support integration of time based media such as audio and video recordings and canvases can have durations as well as heights and widths. This has tremendous potential for publishing richer data sets such as timelines and annotated audio and video recordings. Unfortunately this is beyond the scope of this introductory document but there is an active IIIF A/V Community Group who may be able to provide support.

'''Recommendation:''' If you have an interest in time based media consider joining the [https://iiif.io/community/groups/av/ IIIF A/V Community Group].

Back to [[IIIF|IIIF Home]]

IIIF Background

2025-03-11T10:51:42Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

Part of [[IIIF|IIIF pages]].

Researchers have become accustomed to online access to data about the specimens held in natural history collections. Over several decades metadata standards have been developed to facilitate the sharing and aggregation of these data, notably [https://www.tdwg.org/standards/dwc/ Darwin Core] and [https://www.tdwg.org/standards/abcd/ ABCD] (Access to Biological Collections Data) developed under the auspices of the Biodiversity Information Standards organization ([https://www.tdwg.org/ TDWG]) but other standards developed in other communities, have also proved useful, notably [https://eml.ecoinformatics.org/ EML] (Ecological Metadata Language) from the Ecological Society of America and Long Term Ecological Research Network, and [https://www.ogc.org/standards/gml GML] (Geography Markup Language) from the Open Geospatial Consortium ([https://www.ogc.org/ OGC]).

Data aggregators have arisen who both drive standards development and take advantage of the vast number of records made available through this community effort. Examples include [https://www.ala.org.au/ Atlas of Living Australia], [https://eol.org/ EoL] (Encyclopedia of Life), [https://www.idigbio.org/ iDigBio], [https://gbif.org/ GBIF] (Global Biodiversity Information Facility) and [http://www.worldfloraonline.org/ WFO] (World Flora Online). Aggregators with a wider cultural scope have also shown an interest in representing natural history material, notably [https://www.jstor.org/ JSTOR] and [https://www.europeana.eu/ Europeana].

In addition to these successes there are still many “dark specimens” that are not visible to the web and efforts continue to digitise data on these objects and expose it online.

The vast majority of the data that have been liberated so far have therefore been text based data about specimens and the exchange standards reflect this. But many institutions and projects have simultaneously been imaging their specimens, producing large numbers of images and other media associated with their specimens that they want researchers to be able to access.

Some existing standards have created media extensions to accommodate the sharing of images and other multimedia formats. However, these are restricted to metadata about media objects rather than the exchange of the media objects themselves. For example, two extensions to Darwin Core are [https://tdwg.github.io/ac/introduction/ Audubon Core], (Multimedia Resources Task Group 2013) which is designed to “determine whether a particular resource or collection will be fit for some particular biodiversity science application before acquiring the media.” and the [https://tools.gbif.org/dwca-validator/extension.do?id=gbif:Multimedia Simple Multimedia extension], which is a “simple extension for exchanging metadata about multimedia resources”. Therefore image exchange, in particular, has not used open standards. Projects have relied on transferring high resolution versions of images (e.g. submission of type specimen images to JSTOR) or cut down compressed versions (e.g. many herbarium specimens submitted to The Global Biodiversity Information Facility (GBIF) or to Europeana).

The ''ad hoc'' network of institutions, organisations and projects that has emerged has not allowed access to high resolution versions of images as curated by the host institutions themselves beyond basic links to web pages. If high resolution images have been published in online catalogues, they have been made available using a hotchpotch of different technologies including the now defunct Java Applets and Adobe Flash player. The network has not supported different views of the same specimen or annotations of those views, or integration of audio and moving images.

Natural history collections are not isolated from each other. Most research has to be conducted across collections, because in most cases no one collection holds all the specimens on a taxon. Furthermore, there are many implicit and explicit links between collections. For example, botanical specimens are frequently created in duplicate and distributed to multiple herbaria . In an ideal world a researcher should be able to view and annotate images of specimens held across multiple collections in a unified way, and the host institutions should have access to those annotations and statistics on how their specimens are being used. It should be as if the researcher had the specimens in their hands. How can we achieve this? How can we reduce the barrier to access created by history and geography? This also speaks to the Article 17 of the Convention on Biological Diversity on exchange of information. It states that:

<blockquote>“The Contracting Parties shall facilitate the exchange of information, from all publicly available sources, relevant to the conservation and sustainable use of biological diversity, taking into account the special needs of developing countries”.
</blockquote>
Clearly, facilitating access to high quality images of biological specimens across the internet would at least partially resolve barriers to research in some of the most biodiverse countries.

The notion of sharing and annotating specimen images is not new to the natural history community. [https://www.morphbank.net/ MorphBank], founded in 1998, has grown to allow much of this desirable functionality but at the cost and fragility of being a centralised database. The question we should perhaps be asking is: how can we make the biodiversity data sharing network as a whole more like MorphBank?

The sharing of multimedia representations of objects online is not a problem unique to the biodiversity community. Scholars in museums and archives of all kinds are facing the same issues. In 2011 the [https://www.bl.uk/ British Library], [https://www.stanford.edu/ Stanford University], the [https://www.bodleian.ox.ac.uk/ Bodleian Libraries] (Oxford University), the [https://www.bnf.fr/en Bibliothèque nationale de France, Nasjonalbiblioteket] (National Library of Norway), [https://www.lanl.gov/library/ Los Alamos National Laboratory Research Library], and [https://www.cornell.edu/ Cornell University] came together to develop an exchange standard called IIIF (International Image Interoperability Framework - pronounced “Triple-Eye-Eff”). This framework now consists of six APIs (Application Programming Interface), five stable and one in beta, to publish and integrate image and other multimedia resources in a uniform manner. It has been adopted by many institutions and commercial partners in the digital humanities. Applications based on IIIF enable many of the features desired by biodiversity researchers.

These wiki pages are based on a document which was the culmination of an international project (Synthesys+ Task 4.3) funded by the European Commission that has run from 2019 to 2021. The purpose of Synthesys+ Task 4.3 was to encourage the use of IIIF as a standard way of sharing images of natural history objects and to link this to the CETAF specimen IDs already in use. The task did this by establishing exemplar implementations (subtask 4.3.1) and documenting our experiences in the form of a document to apply IIIF to other collections (subtasks 4.3.2 and 4.3.3).

Back to [[IIIF|IIIF pages]].

IIIF

2025-03-11T10:51:30Z

D.Fichtmüller: imported from old CETAF Identifier Wiki, page originally created by Roger Hyam

__TOC__

= Implementation of IIIF for Natural History Collections =

The CETAF Identifier specification provides a uniform way for people and machines to access textual data about specimens over the internet but one of the primary use cases is to access images of specimens. These pages document best practice for exposing specimen images using IIIF and why this approach is recommended. The initial development of these recommendations was carried out as part of an EU funded Synthesys+ Task 4.3 (2019-2021) which was part of the larger [https://www.dissco.eu/ DISSCo] initiative.

IIIF ([https://iiif.io/ International Image Interoperability Framework]) is an exchange standard for sharing multimedia representations of objects on-line. It has been adopted by many institutions and commercial partners in the digital humanities community but, before Synthesys+ Task 4.3, was not used in the Natural History community.

There is quite a lot of information here so it is split across multiple pages.

== Introduction ==

* [[IIIF Background]] - Why IIIF looks like the right fit for Natural History Specimens.
* [[IIIF Framework]] - An overview of the IIIF Framework including the standards and organisation.

== Linking ==

* [[IIIF Linking HTML]] - How to link to and from a IIIF Manifest and a HTML page.
* [[IIIF Linking CETAF IDs]] - How to link to and from a IIIF Manifest and CETAF ID.
* [[IIIF Linking Darwin Core]] - How to link from Darwin Core Archive files to IIIF Manifests
* [[IIIF Linking ABCD]] - How to link from ABCD metadata to a IIIF Manifest
* [[IIIF Linking CSV]] - Linking from generic CSV download files.

== Deployments ==

=== Case Studies ===

* [[IIIF RBGE Example]] - How IIIF is implemented at the Royal Botanic Garden Edinburgh (E)
* [[IIIF Herbaria Mundi]] - An example of combining IIIF resources from multiple sources
* [[IIIF BGBM Example]] - How IIIF is implemented at the Botanic Garden and Botanical Museum Berlin (B)
* [[IIIF MfN Example]] - How IIIF is implemented at Museum für Naturkunde Berlin
* [[IIIF Meise Example]] - How IIIF is implemented at Meise Botanic Garden

=== Installations ===

==== Royal Botanic Garden Edinburgh (E) ====

* Status: IIIF end point in production.
* Example CETAF ID: https://data.rbge.org.uk/herb/E00008781
* Example IIIF Manifest: https://iiif.rbge.org.uk/herb/iiif/E00008781/manifest

==== Botanic Garden and Botanical Museum Berlin (B) ====

* Status: IIIF end point in production.
* Example CETAF ID: https://herbarium.bgbm.org/object/B200012401
* Example IIIF Manifest: https://herbarium.bgbm.org/data/iiif/B200012401/manifest.json

==== Museum für Naturkunde Berlin (MfN) ====

* Status: IIIF end point in production.
* Developers actively contributing to IIIF viewer code bases.
* Example CETAF ID: https://portal.museumfuernaturkunde.berlin/detail/a3293da550fafbcd706e
* Example IIIF Manifest: https://portal.museumfuernaturkunde.berlin/api/v1/iiif/manifest/a3293da550fafbcd706e/manifest.json

==== Meise Botanic Gardens ====

* Status: IIIF end point in production.
* Example CETAF ID: https://www.botanicalcollections.be/specimen/BR0000022705044
* Example IIIF Manifest: http://iiif-manifest.oxalis.br.fgov.be/specimen/BR0000022705044/manifest

==== Asociación Jardín Botánico La Laguna (LAGU) ====

* Status: IIIF in production.
* Example CETAF ID: http://lagu.jacq.org/object/PG-03584
* Example IIIF Manifest: http://lagu.jacq.org/iiif/PG-03584

==== Institute of Botany, Ilia State University (TBI) ====

* Status: IIIF in production.
* Example CETAF ID: http://tbi.jacq.org/object/TBI1038592
* Example IIIF Manifest: http://tbi.jacq.org/iiif/TBI1038592

==== Herbarium Rita & Eckhard Willing Herbarium ====

* Status: IIIF end point in production.
* Example CETAF ID: https://willing.jacq.org/object/JACQID1184346
* Example IIIF Manifest: http://willing.jacq.org/iiif/JACQID1184346

==== Finish Museum of Natural History (Luomus) ====

* Status: IIIF near production. Image API in place Presentation API to follow.
* Example CETAF ID: http://id.luomus.fi/KN.17856
* Example IIIF Image: https://iiif-laji.rahtiapp.fi/iiif/3/MM.1619624/info.json

==== University of Leipzig, Herbarium (LZ) ====

* Status: IIIF in production.
* Example CETAF ID: https://lz.jacq.org/LZ012400
* Example manifest: https://sammlungen-editor.uni-leipzig.de/api/iiif/presentation/v2/ULBotanyHerbarium_derivate_00003357/manifest

==== NHM Vienna (W) ====

* Status: Cantaloupe and IIPSrv are setup in a testbed Mirador vs. UniverslViewer are evaluated and final decision on server and viewer before Q4 2022.
* Example CETAF ID: https://w.jacq.org/W0100330

==== University of Vienna, Herbarium (WU) ====

* Status: IIIF in production.
* Example CETAF ID: https://wu.jacq.org/WU0044029
* Example combined manifest: Image and CMS JACQ "Metadata" https://services.jacq.org/jacq-services/rest/iiif/manifest/142213
* Example image manifest: https://app05a.phaidra.org/manifests/WU0044029

ISTC DWG Meeting Spring 2018 Copenhagen

2025-03-05T14:17:59Z

D.Fichtmüller: links to local version of openmedia files

= Joint CETAF ISTC and Digitisation Working Group Meeting, Copenhagen 21-22 February 2018 =
== Attendance ==
* Quentin Groom (Meise)
* Anton Güntsch (BGBM)
* Patricia Mergen (RMCA / Meise)
* Dominik Röpert (BGBM)
* Wouter Addink (Naturalis)
* Ana Casino (CETAF)
* Karsten Gödderz (CETAF)
* Björn Quast (ZFMK)
* Falko Glöckler (MfN Berlin)
* Dagmar Triebel (SNSB)
* Ingimar Erlingsson (Swedish Museum of Natural History)
* Elspeth Haston (RBGE)
* Wilfred Gerritsen (Naturalis)
* Sarah Phillips (Kew)
* Dare Talvitie (Finnish Museum of Natural History)
* Jere Kahanpää (Finnish Museum of Natural History)
* Jiří Frank (Prague)
* Martin Soucek (Prague)
* Jörg Lange (Stuttgart)
* Simon Chagnoux (Paris)
* Heimo Rainer (Vienna)
* Christian Steinwender (Vienna)

== Agenda ==
'''February 21'''
=== ISTC (13:00 - 17:00) ===
{|
|-
| '''13:00''' || Welcome, introduction of participants, and adoption of agenda (Anton Güntsch)
|-
| 13:15 || Stable IDs - summary of activities in 2017 [discussion of next steps] (Anton Güntsch, [[:File:ISTC_2018_Copenhagen_Guentsch_Identifier.pdf|presentation]])
|-
| 14:00 || The Netherlands Biodiversity API (Wilfred Gerritsen, [[:File:ISTC_2018_Gerritsen_NBA.pdf|presentation]])
|-
| 14:30 || Die Herbonauten [discussion: collaboration of citizen science platforms in CETAF] (Dominik Röpert, [[:File:ISTC_2018_Roepert_Herbonauten.pdf|presentation]])
|-
| 14:45 || ICEDIG (Quentin Groom, [[:File:ISTC_2018_Groom_ICEDIG.pdf|presentation]])
|-
| '''15:00''' || Coffee
|-
| 15:30 || other projects: IndExs - Index of Exsiccatae (Dagmar Triebel, [[:File:ISTC_2018_Triebel_IndExs.pdf|presentation]])
|-
| 15:45 || other projects: MORPHYLL: A database of fossil leaves and their morphological traits (Jörg Lange, [[:File:ISTC_2018_Lange_Morphyll.pdf|presentation]])
|-
| 16:00 || The CETAF Strategy and Development Plan (2015-2025) [review and discussion, see https://cetaf.org/sites/default/files/final_strategy_and_strategic_development_plan.pdf] (All)
|-
| 16:30 || DiSSCo [alignment of ISTC activities with DiSSCo] (Wouter Addink, [[:File:ISTC_2018_Addink_DiSSCo.pdf|presentation]])
|-
| 16:50 || EU Opportunities (Patricia Mergen [[:File:ISTC_2018_Mergen_EU-Opportunities.pdf|presentation]])
|-
| 17:10 || SYNTHESYS+ [Overview of ISTC-related activities] (All)
|-
| 17:30 || AOB and next meeting(s) (All)
|-
| '''17:45''' || End of (ISTC) meeting
|}

'''19:00 Dinner'''
 RizRaz
 Store Kannikestræde 19
 1169 København K

'''February 22'''

=== Digitisation Working Group (9:00 - 13:00) ===

{|
|-
| '''09:00''' || Welcome, introduction of participants, and adoption of agenda (Elspeth Haston)
|-
| 09:15 || Review of digitisation based on recent surveys ()
|-
| || 1) Digitisation Resources & Gap Analysis Survey (Elspeth Haston, [[:File:Digitisation_resources_gap_analysis.pdf|presentation]])
|-
| || 2) SYNTHESYS3 State of Digitisation survey (Sarah Phillips, [[:File:Digitisation_Working_Group_syntheys_Survey.pdf|presentation]])
|-
| 10:15 || Digitisation Definition for Collections (All, [[:File:Digitisation_definitions_for_collections.pdf|presentation]])
|-
| 10:30 || The CETAF Strategy and Development Plan (2015-2025) [review and discussion, see https://cetaf.org/sites/default/files/final_strategy_and_strategic_development_plan.pdf] (All)
|-
| '''11:00''' || Coffee
|-
| 11:30 || SYNTHESYS+ continued (All)
|-
| 12:30 || AOB and next meeting(s) (All)
|-
| '''13:00''' || End of (DWG) meeting
|}

== Minutes ==
[[:File:CETAF_ISTC_DWG_2018_Minutes_Final.pdf download (pdf)]

== Logistics ==
=== Venue ===
Natural History Museum of Denmark 
Administration 
Gothersgade 130 
DK-1123 Copenhagen

=== Transport ===
==== By public transport to Nørreport Station ====
The venue is in close proximity (ca. 3 minutes walk) to Nørreport Station, the main hub of public transport in Copenhagen. The next crossing is Nørre Voldgade/Gothersgade, with the Botanical Garden's main entrance at the facing corner.

==== From the airport ====
The the metro from the airport (Terminal 3) to Nørreport Station (ca. 15 minutes; there are only two metro routes, both will go to Nørreport Station). You will need a ticket valid for three zones (DKK 36.00). For guidance from Nørreport Station.
Taxi from the airport to Gothersgade 130 (ca. 25 minutes) will cost about DKK 250.

==== By train ====
Many trains will go directly to Nørreport Station. If yours doesn't, take bus **5C** headed for **Husum Torv** or **Herlev Hospital** or S-Train **A** headed for **Farum St.** from Copenhagen Central Station (Hovedbanegården) to Nørreport Station. Busses will go roughly every 5 minutes, the S-Train every 10-15 minutes. You will need a ticket valid for two zones (DKK 24.00).

A useful route planner for public transport is: https://www.rejseplanen.dk/webapp/index.html?language=en_EN

=== Map ===
[[:File:ISTC_DWG_2018_Map.png|Download]]

=== Hotels ===
'''Hotel Arthur''' (http://www.arthurhotels.dk/hotel-kong-arthur/) ca. DKK 1000/night 
'''Ibsens Hotel''' (http://www.arthurhotels.dk/ibsens-hotel/) ca. DKK 850/night 
'''Hotel Christian''' IV (https://www.hotelchristianiv.dk/en/) ca. DKK 900/night 
'''Hotel Nora''' (http://www.hotelnora.dk) ca. DKK 900/night 

There is good public transport in Copenhagen, and the venue is close to Nørreport Station, so it should be relatively easy to get to the meeting form hotels farther away.

ISTC DWG Meeting Spring 2019 Vienna

2025-03-05T14:13:07Z

D.Fichtmüller: links to local version of openmedia files

= Joint CETAF ISTC and Digitisation Working Group Meeting, Vienna 13-14 February 2019 =
== Attendance ==
* Anton Güntsch (BGBM Berlin)
* Elspeth Haston (RBGE)
* Heimo Rainer (Vienna)
* Dominik Röpert (BGBM Berlin)
* Peter Grobe (ZFMK)
* Björn Quast (ZFMK)
* Martin Stein (Copenhagen)
* Dagmar Triebel (SNSB)
* Mathias Dillen (Meise)
* Ayco Holleman (Naturalis)
* Alex Hardisty (Cardiff)
* Roger Hyam (RBGE)
* Falko Glöckler (MfN Berlin)
* Simon Chagnoux (Paris)
* Wouter Addink (Naturalis)
* Frederik Berger (MfN Berlin)
* Laurence Livermore (NHM)
* Celia Santos (CSIC)
* Patrik Mráz (Charles University, Prague)
* Patricia Mergen (Meise/Tervuren)
* Ana Casino (CETAF)
* Carlos Monje (SMNS Stuttgart)
* Joachim Holstein (SMNS Stuttgart)
* Karol Marhold (Bratislava)
* Xavier Vermeersch (CETAF)
* Thomas Hörnschemeyer (Senckenberg)
* Luc Willemse (Naturalis)
* Jiri Frank (NM, Prague)
* Anne Koivunen (UH, Luomus)
* Claudia Kamcke (Braunschweig)

== Draft agenda ==
'''February 13'''
=== ISTC (13:00 - 18:00) ===

{|
|-
| '''13:00''' || Welcome, introduction of participants, adoption of agenda (A. Güntsch)
|-
| 13:20 || QoS workshop Copenhagen - report, next steps
|-
| || - "Botany Pilot" (D. Röpert)
|-
| || - ID Implementers Registry (A. Güntsch, see [https://docs.google.com/spreadsheets/d/1vHl2xDghffm6HfQhVeruHV6ZAWAnrc-2LPasq0fOyF4/edit#gid=83189964 draft registry])
|-
| || - CETAF Specimen URI Tester - new developments (R. Hyam, see [http://herbal.rbge.info/ URI Tester] and [http://iiif.rbge.info/ iiiF])
|-
| || - Semantic enrichment of collector information (M. Dillen, [[:File:Sementic_enrichment_of_collector_information.pdf|presentation]])
|-
| '''14:20''' || Coffee break
|-
| 14:50 || DiSSCo Technical Infrastructure
|-
| || - Infrastructure overview (A. Hardisty)
|-
| || - Discussion (central vs distributed services?, responsibilities and role of natural history collections?, role of CETAF IDs for specimens?, joint activities?, other questions?)
|-
| 16:00 || DiSSCo related activities
|-
| || - COST Mobilise WG4 "Development of Standards and Guidelines for data archiving and long-term preservation" (D. Triebel, [[:File:COST_Mobilise_WG4_-_Development_of_Standards_and_Guidelines_for_data_archiving_and_long-term_preservation.pdf|presentation]])
|-
| || - GeoCASe – current situation and next steps (F. Glöckler)
|-
| || - COST Mobilise Person ID workshop (E. Haston)
|-
| 16:45 || On the Way from Nagoya to Legal Handling of Accession Units in collections: Management of ABS codes in Diversity Workbench (P. Grobe, [[:File:On_the_Way_from_Nagoya_to_Legal_Handling_of_Accession_Units_in_collections.pdf|presentation]])
|-
| 17:00 || CETAF strategy and development plan - targets and activities
|-
| 17:45 || AOB, next meetings
|-
| '''18:00''' || End of (ISTC) meeting
|}

'''19:00 Dinner''' || [https://www.diehalle.at/ HALLE Café Restaurant] - [https://goo.gl/maps/DrDA1CnogDF2 location: Museumsplatz 1, 1070 Wien]

'''February 14'''

=== Digitisation Working Group (9:00 - 13:00) ===

{|
|-
| '''09:00''' || Welcome, introduction of participants, adoption of agenda (E Haston)
|-
| 09:15 || CETAF strategy and development plan - targets and activities (E Haston & A Güntsch)
|-
| 09:30 || Minimal Information for Digital Specimens (MIDS) (A Hardisty)
|-
| '''10:30''' || Coffee Break
|-
| 11:00 || Review of digitisation within DiSSCO-related projects and work programs
|-
| || - SYNTHESYS+ (E Haston & General Discussion)
|-
| || - ICEDIG survey results (X Vermeersch)
|-
| || - MOBILISE (E Haston & General Discussion)
|-
| 12:30 || CETAF Collections Group (C Quaisser)
|-
| 12:45 || AOB, next meetings
|-
| '''13:00''' || End of DWG meeting
|}

== Minutes ==
[[:File:Minutes_of_the_CETAF_ISTC-DWG_meeting%2C_Vienna_2019.pdf|download(pdf)]]

== Logistics ==
=== Venue ===
Natural History Museum Vienna 
Burgring 7 
AT-1010 Vienna

The venue is located just outside and opposite of subway Station VOLKSTHEATER - exit "Ring/Museen".
=== Transport ===
==== Arrival ====
==== From the airport ====
At the airport you will find green signs once getting out that lead you to a direct train connection called '''CAT (City Airport Train)'''.
It runs every 30 minutes HH:09 and HH:39 nonstop to the "Wien Mitte Landstraße" single € 11 € return € 19
https://www.cityairporttrain.com/en/home

From there continue to the Museum using the orange subway line U3 direction Ottakring towards "Volkstheater".

==== By train ====
Nowadays trains main arrival point is '''Wien Hauptbahnhof'''. From there you can use subway line U1 to Stephansplatz change for subway number U3 to Volkstheater
A second less frequent stop is Westbahnhof. From there you can directly connect to the NHM using subway U3, again to Volkstheater.

==== During Your Stay ====
==== Public transport ====
The public transport system in Vienna is dense. Tickets can be purchased at counters of bigger stations, at the airport, railway stations or online
https://shop.wienerlinien.at/index.php/tickets

A useful route planner for public transport is @ https://www.wienerlinien.at/eportal3/ep/tab.do?tabId=0
Available also as a mobile App '''QANDO''' https://m.qando.at

=== Map ===
[https://goo.gl/maps/FgBYyyVNegk View Map]
=== Hotels ===
IBIS - https://www.accorhotels.com/gb/hotel-0796-ibis-wien-mariahilf/index.shtml
MERCURE - https://www.accorhotels.com/gb/hotel-5358-hotel-mercure-wien-westbahnhof/index.shtml
LEONARDO - https://www.leonardo-hotels.com/leonardo-hotel-vienna
Pension Wild - https://www.pension-wild.com/en/

all available direct or via booking.com / Expedia / trivago etc.

ISTC Meeting Spring 2017 Stuttgart

2025-03-05T14:12:11Z

D.Fichtmüller: links to local version of openmedia files

{{NO_TITLE}}
'''<big>''Joint CETAF Digitisation and ISTC Group Meeting, Stuttgart''</big>'''
'''<big>27-28 March 2017</big>'''

== Attendance ==
* Wouter Addink (Leiden)
* Ana Casino (CETAF)
* Simon Chagnoux (Paris)
* Johanna Eder (Stuttgart)
* Jiří Frank (Prague)
* Katarina Gatialova (Prague)
* Falko Glöckler (Berlin, MfN)
* Karsten Gödderz (CETAF)
* Peter Grobe (Bonn)
* Quentin Groom (Meise)
* Anton Güntsch (Berlin, BGBM)
* Thomas Hörnschemeyer (Frankfurt)
* Joachim Holstein (Stuttgart)
* Jana Hoffmann (Berlin, MfN)
* Ayco Holleman (Leiden)
* Jiří Kvacek (Prague)
* Patricia Mergen (Brussels / Tervuren)
* Juan Carlos Monje (Stuttgart)
* Björn Quast (Bonn)
* Dominik Röpert (Berlin, BGBM)
* Martin Stein (Copenhagen)
* Christian Steinwender (Vienna)
* Ari Taponen (Helsinki)
* Dagmar Triebel (Munich)
* Marie-Hélène Weech (London, Kew)

== Agenda ==

=== March 27 ===

''' 9:00 - 12:00 Identifiers Implementers Group '''

Expected outcome:
* Summary of progress made in 2016.
* A clear implementation plan for 2017.
* Assignment of tasks.

''' ISTC Meeting '''

{|
|-
| '''13:00''' || Welcome, introduction of participants, and adoption of agenda (Johanna Eder, Anton Güntsch)
|-
| 13:15 || Report from identifier initiative, discussion of next steps (Anton Güntsch, [[:File:ISTC_2017_Guentsch_Identifier.pdf|presentation]])
|-
| 13:45 || Report from LOD Hackathon, discussion of next steps and collaboration opportunities (Ayco Holleman, [[:File:ISTC_2017_Hollemann_LOD.pdf|presentation]])
|-
| 14:00 || Other ISTC/CETAF initiatives
|-
| || Herbadrop (Simon Chagnoux, [[:File:ISTC_2017_Chagnoux_Herbadrop.pdf|presentation]])
|-
| || BHL-E (Jiří Frank, [[:File:ISTC_2017_Frank_BHL.pdf|presentation]])
|-
| || Geo-referencing (Ayco Holleman)
|-
| 14:30 || Other developments of ISTC members
|-
| || Common name services (Christian Steinwender)
|-
| || GFBio pipelines for collection data (Dagmar Triebel, [[:File:ISTC_2017_Triebel_GFBio.pdf|presentation]])
|-
| || MNHN Collection website and 3d gallery (Simon Chagnoux)
|-
| || Collection portal developments at the Botanic Garden Meise (Quentin Groom, [[:File:ISTC_2017_Groom_Specimen-Portal.pdf|presentation]])
|-
| '''15:15''' || Coffee
|-
| 15:45 || TDWG Biodiversity Information Standards (Quentin Groom, [[:File:ISTC_2017_Groom_TDWG.pdf|presentation]])
|-
| 16:00 || DiSSCo (Wouter Addink, [[:File:ISTC_2017_Addink_DiSSCo.pdf|presentation]])
|-
| 16:20 || EU Funding opportunities (Patricia Mergen)
|-
| 16:50 || Ideas for collaboration, next meeting(s) (All)
|-
| '''17:00''' || End of (ISTC) meeting
|}

'''19:00 Dinner'''
Theaterhaus Stuttgart, Siemensstraße 11, 70469 Stuttgart, https://www.plankenhorn-stengel.de/

=== March 28 ===

'''Digitisation Working Group '''
{|
|-
| '''9:00''' || Welcome, introduction of participants, request for AOB items and adoption of agenda
|-
| '''9:15''' || CETAF Strategy & Targets (All)
|-
| || Review all 25 CETAF Targets and identify relevant targets for the Digitsation Working Group and ISTC
|-
| || Decide how to include CETAF Strategy within the Digitisation Working Group Framework & Aims
|-
| '''9:45''' || Update on SYNTHESYS digitisation (Elspeth Haston, [[:File:CETAF_DWG_Stuttgart_March_2017_SYNTHESYS3_JRA_update.pdf|presentation]])
|-
| || Communication of outputs from project
|-
| '''10:10''' || Digitisation at the Naturkundemuseum, Stuttgart (Joachim Holstein, [[:File:Digitisation-at-SMNS_2017.pdf|presentation]])
|-
| '''10:30''' || Implementation of Stable IDs in the physical collection. Implications for collection workflow (Falko Glöckler, [[:File:Gloeckler_use_cases_of_stable_URIs.pdf|presentation]])
|-
| '''11:00''' || Coffee
|-
| '''11:30''' || Digitisation Resources Gap Analysis (Elspeth Haston)
|-
| || Review draft survey
|-
| || Decide on content and structure of survey and plan the schedule
|-
| '''12:20''' || CETAF Proposal for COST Action: MOBILISE (Dagmar Triebel, [[:File:COST_presentation_CETAF-DWG-2017-03-28.pdf|presentation]])
|-
| '''12:30''' || Ideas for collaboration, next meeting(s) (All)
|-
| '''12:45''' || AOB
|-
| '''13:00''' || End of (DWG) meeting
|}

== Minutes ==
Minutes written by Elspeth Haston and Anton Güntsch: [[:File:MinutesofthejointCETAFDigitisationGroupandISTCMeetingStuttgart27-28March2017_(1).pdf|download]]

== Logistics ==

=== Venue ===
Lecture hall of the 
Staatliches Museum für Naturkunde Stuttgart 
Museum am Löwentor 
Rosenstein 1 
70191 Stuttgart 

Next to '''station "Nordbahnhof"''' close to the entrance of the "Rosensteinpark".

=== Directions ===
http://www.naturkundemuseum-bw.de/visit/directions

=== Hotels ===

* Ibis Budget Stuttgart, Siemensstraße 28, 70469 Stuttgart, http://www.accorhotels.com/de/hotel-5441-ibis-budget-stuttgart-city-nord/index.shtml
* Motel One Stuttgart (3 options), Tel. : +49/711/218 402 00, http://www.motel-one.com/de/hotels/stuttgart/
** Heilbronnerstraße 325, 70469 Stuttgart
** Lautenschlagerstraße 14, 70173 Stuttgart
** Badstraße 20, 70372 Stuttgart
* Stadthotel Weinsberg, Grazer Straße 32, 70469 Stuttgart-Feuerbach, http://www.ows.stadthotel-weinsberg.de/x1y8858z4543721/
* Hotel Geiger, Wilhelm-Geiger-Platz, 70469 Stuttgart-Feuerbach, http://www.hotelgeiger.de/
* Hotel Rieker, Friedrichstraße 3, 70174 Stuttgart, Tel: 0711/ 221311, Fax: 0711/ 293894, http://www.hotel-stuttgart-rieker.de
* Hotel Mercure Stuttgart City Center, Heilbronner Str. 88, 70191 Stuttgart, Tel: 0711/255580, Fax : 0711/25558100, http://www.mercure.com/de/hotel-5424-mercure-hotel-stuttgart-city center/index.shtml
* Hotel Kronen-Hotel, Kronenstrasse 48, 70174 Stuttgart, Tel: 0711/ 22510, Fax: 0711/ 2251404, http://www.kronenhotel-stuttgart.de
* Hotel Unger, Kronenstraße 17, 70173 Stuttgart, Tel: 0711 20990, Fax: 0711 2099100, http://www.hotel-unger.de

File:ISTC 2018 Triebel IndExs.pdf

2025-03-05T13:55:40Z

D.Fichtmüller: Undo revision 1489 by WikiSysop (talk)

==Summary==
{{Information
|description=Index of Exsiccatae
|date=2018-02-21
|source=Dagmar Triebel
|author=Dagmar Triebel
|permission=
|other versions=
}}

==License==
{{cc-by-sa-4.0}}

[[Category:Uploaded with UploadWizard]]

File:CETAF ISTC DWG 2018 Minutes Final.pdf

2025-03-05T13:55:31Z

D.Fichtmüller: Undo revision 1488 by WikiSysop (talk)

==Summary==
{{Information
|description=Minutes of the joined CETAF ISTC and DWG meeting 2018
|date=2018-03-27
|source=Own work
|author=[[User:Anton Güntsch|Anton Güntsch]]
|permission=
|other versions=
}}

==License==
{{cc-by-sa-4.0}}

[[Category:Uploaded with UploadWizard]]

File:Digitisation-at-SMNS 2017.pdf

2025-03-05T13:55:21Z

D.Fichtmüller: Undo revision 1487 by WikiSysop (talk)

==Summary==
{{Information
|description=Presentation about the digitisation at SMNS to the CETAF Digitsation Working Group in March 2017
|date=2017-04-10
|source=Digital presentation at meeting
|author=Joachim Holstein
|permission=
|other versions=
}}

==License==
{{cc-by-sa-3.0}}

[[Category:Uploaded with UploadWizard]]

File:ISTC 2018 Addink DiSSCo.pdf

2025-03-05T13:55:12Z

D.Fichtmüller: Undo revision 1486 by WikiSysop (talk)

==Summary==
{{Information
|description=DiSSCo
|date=2018-02-22
|source=Wouter Addink
|author=Wouter Addink
|permission=
|other versions=
}}

==License==
{{cc-by-sa-4.0}}

[[Category:Uploaded with UploadWizard]]

File:COST Mobilise WG4 - Development of Standards and Guidelines for data archiving and long-term preservation.pdf

2025-03-05T13:54:56Z

D.Fichtmüller: Undo revision 1485 by WikiSysop (talk)

==Summary==
{{Information
|description=Presentation: COST Mobilise WG4 "Development of Standards and Guidelines for data archiving and long-term preservation"
|date=2019-02-13
|source=Personal communication
|author=Dagmar Triebel
|permission=
|other versions=
}}

==License==
{{cc-by-4.0}}

[[Category:Uploaded with UploadWizard]]

File:ISTC 2018 Lange Morphyll.pdf

2025-03-05T13:54:48Z

D.Fichtmüller: Undo revision 1484 by WikiSysop (talk)

==Summary==
{{Information
|description=Morphyll
|date=2018-02-21
|source=Jörg Lange
|author=Jörg Lange
|permission=
|other versions=
}}

==License==
{{cc-by-sa-4.0}}

[[Category:Uploaded with UploadWizard]]

File:ISTC 2018 Groom ICEDIG.pdf

2025-03-05T13:54:40Z

D.Fichtmüller: Undo revision 1483 by WikiSysop (talk)

==Summary==
{{Information
|description=ICEDIG
|date=2018-02-21
|source=Quentin Groom
|author=Quentin Groom
|permission=
|other versions=
}}

==License==
{{cc-by-sa-4.0}}

[[Category:Uploaded with UploadWizard]]

File:ISTC 2018 Roepert Herbonauten.pdf

2025-03-05T13:54:32Z

D.Fichtmüller: Undo revision 1482 by WikiSysop (talk)

==Summary==
{{Information
|description=Die Herbonauten
|date=2018-02-21
|source=Dominik Röpert
|author=Dominik Röpert
|permission=
|other versions=
}}

==License==
{{cc-by-sa-4.0}}

[[Category:Uploaded with UploadWizard]]

File:COST presentation CETAF-DWG-2017-03-28.pdf

2025-03-05T13:54:23Z

D.Fichtmüller: Undo revision 1481 by WikiSysop (talk)

==Summary==
{{Information
|description=Presentation about the COST proposal to the CETAF Digitsation Working Group in March 2017
|date=2017-04-10
|source=Digital presentation at meeting
|author=Dagmar Triebel
|permission=
|other versions=
}}

==License==
{{cc-by-sa-3.0}}

[[Category:Uploaded with UploadWizard]]

File:ISTC 2018 Gerritsen NBA.pdf

2025-03-05T13:54:11Z

D.Fichtmüller: Undo revision 1480 by WikiSysop (talk)

==Summary==
{{Information
|description=Netherlands Biodiversity Data Services
|date=2018-02-21
|source=Wilfred Gerritsen
|author=Wilfred Gerritsen
|permission=
|other versions=
}}

==License==
{{cc-by-sa-4.0}}

[[Category:Uploaded with UploadWizard]]

File:ISTC 2018 Copenhagen Guentsch Identifier.pdf

2025-03-05T13:53:41Z

D.Fichtmüller: Undo revision 1479 by WikiSysop (talk)

==Summary==
{{Information
|description=CETAF Identifiers
|date=2018-02-21
|source=Own work
|author=[[User:Anton Güntsch|Anton Güntsch]]
|permission=
|other versions=
}}

==License==
{{cc-by-sa-4.0}}

[[Category:Uploaded with UploadWizard]]

Best practices for stable URIs

2025-03-05T13:23:00Z

D.Fichtmüller: removed call to request accounts

'''This page is a copy from https://wiki.pro-ibiosphere.eu/wiki/Best_practices_for_stable_URIs , which is not available anymore. An archived version can be found at the [https://web.archive.org/web/20210308093304/https://wiki.pro-ibiosphere.eu/wiki/Best_practices_for_stable_URIs Internet Archive].'''

<table><tr><td style="width:50%">__TOC__</td><td style="width:50%; text-align:right; vertical-align:top">Recommended citation: Gregor Hagedorn, Terry Catapano, Anton Güntsch, Daniel Mietchen, Dag Endresen, Soraya Sierra, Quentin Groom, Jordan Biserkov, Falko Glöckler & Robert Morris, 2013. Best practices for stable URIs http://wiki.pro-ibiosphere.eu/wiki/Best_practices_for_stable_URIs.</td></tr></table>

==Introduction==

1. It is important to keep the mission-critical URIs (or URLs, or IRIs, or web-adresses) stable. Make a deliberate choice which pages and which classes of objects you want to manage as stable. Do not aim to keep all your URIs stable forever: this may become unmanageable.

2. The primary purpose of this discussion is to support others in finding good URI patterns. The secondary purpose is to assess whether it is possible that '''some institutions voluntarily share the same pattern to ease recognition and set a recognizable example for others to follow?'''

3. Linked Open Data and the Semantic Web in particular use http-URIs to identify resources as well as to retrieve information about them. The Semantic Web works with any kind of http-URIs, including those that do not follow these best practices. However, it works best if URIs are kept stable. This can be difficult for some URI patterns; the present discussion makes suggestions how to make it reasonably likely to be able to keep your URIs stable.

4. While the present discussion may be useful when looking for stable URIs patterns for other purposes than Linked Open Data and the Semantic Web, it largely focuses on these and some aspects are specific to the Semantic Web.

5. '''Keep the URI very simple right from the start.''' In the face of changing technology, at some point you will have to use the webserver's rewrite module to keep URIs stable. The simpler the URI pattern is, the easier this becomes. Thus the first recommendation is: Create a simple URI and use rewriting right from the start. Define simple URI patterns (= no ports, no extensions like .php or .aspx, no parameters with ? or &) that are being rewritten to your current technology.

6. If several different URIs exist within a particular dereferencing service (e.g. two http-URIs) that point to exactly the same resource:
# Declare one as the "preferred" (canonical) URI.
# Inform about the equivalence either through redirects (e.g. http status 301) or through owl:sameAs or skos:closeMatch statements in associated rdf.

7. Highly recommended references:
* [http://www.w3.org/TR/cooluris/ Sauermann & Cyganiak 2008, Cool URIs for the Semantic Web].
* Hyam, R.D., Drinkwater, R.E. & Harris, D.J. Stable citations for herbarium specimens on the internet: an illustration from a taxonomic revision of Duboscia (Malvaceae) Phytotaxa 73: 17–30 (2012) [http://www.mapress.com/phytotaxa/content/2012/f/pt00073p030.pdf PDF]
* [http://stories.rbge.org.uk/archives/3846 Stable Identifiers for Specimens Workshop] (Roger Hyam, Edinburgh).
* [http://links.gbif.org/persistent_identifiers_guide_en_v1.pdf Kevin Richards, Richard White, Nicola Nicolson, Richard Pyle 2011 A Beginner’s Guide to Persistent Identifiers] (good general discussion, but most solutions discussed would not function in a Linked Data world).
* [http://obofoundry.org/id-policy.shtml OBO Foundry Identifier Policy].

==Recommended patterns for stable URIs==

A generally recommended URI pattern is the following:
: '''http://subdomain.yourdomain.org/path/variable-identifier'''
For the '''Semantic Web''' and '''Linked Open Data''', the URI for the abstract concept/physical object and the URI for the related information resource (html, RDF, json) may be two independent URIs of the form above connected by an http 303 (“see also”) redirect. Alternatively, a URI like the above may be used for the information resource plus a “hash-URI” for the abstract concept/physical object. A hash URI appends a fragment identifier at the end:
: '''http://subdomain.yourdomain.org/path/variable-identifier#hash'''
* http:// is called a "scheme". The semantic web requires http here (nothing else, not even https!).
* '''subdomain''': If the stable URIs use a general purpose domain with many different services, it may be desirable to add a dedicated subdomain for specific services. The use of subdomains offers the flexibility that in the future several institutions share or merge their operations for a set of subdomains without affecting the stability of these URIs. If the main domain is already dedicated to a specific service, the use of a subdomain is irrelevant.
* '''yourdomain.org/''': The main domain name, like rbge.org.uk, zoobank.org, ipni.org, naturalis.nl, nhm.ac.uk/ . This provides global uniqueness of any locally unique string following it, anchors trust and authority of the information, and provides branding and traceability of citations.
*: Note: The scheme and domain part of URIs (e.g. http://subdomain.yourdomain.org/) is case-insensitive. For example, three URIs containing "subdomain", "Subdomain", and "SUBDOMAIN" would point to the same resource. For the semantic web, however, this part should always be entirely in lowercase letters. All other parts (part, identifier) are required to be case sensitive
* '''path''': The part that remains constant for different identifiers of the same class (e.g., taxa, specimens). Similar to a subdomain, this increases the ease with which identifiers can be kept stable over decades (using web server rewrite modules).
*: The path may consist of several parts like “/specimen/id/” or When using a pattern without a path like [http://zoobank.org/7D39CAAA-4B4B-4588-A372-D4097162B1CD http://zoobank.org/7D39CAAA-4B4B-4588-A372-D4097162B1CD], the variable-identifier part after the domain must have a form which can always be distinguished from any other possible path or service on the same domain. In the example above, both the homogeneous length of a UUID, the formatting with hyphens and the absence of any other punctuation makes this likely. In most circumstances it is not recommended to omit a path on institutional domains (for which the number of other services may be very large).
*: It is not required, but best practive that the path should not contain a colon (:). While in principle legal, the colon does create problems when a relative URI starts with a colon in the first part of the path. Relative URIs may be unavoidable if both http and https schemas are to be supported for human readable html. Also, some bugs in relation to colon in the path may exist with particular software.
* '''variable-identifier''': The part that changes for each object. It will usually be a number or code you also use otherwise, like a simple locally unique or code (123, a123, M-2361318, ...) or it may be a UUID like 1C4EDC178AD79DD7F1A5AB856E8C5BCA.
*: Best practice for choosing this identifier are to use an existing scheme for which uniqueness within a project or institution is already managed. If an object or concept code exist, if for specimen it is perhaps already attached by QR- or barcodes to specimens, this should be used. The following explains some advantages and disadvantages of certain choices:
*:* Short incremental identifiers or codes have some examples if you expect use cases in which codes must be compared with each other by human for identity, entered via a keyboard, or encoded in barcodes or QR codes (the physical size of the encoding increases with the number of characters). The disadvantage of these codes is that they can generally only be guaranteed to be unique if they are only created while a data connection to a central code registry exists.
*:* Long UUID codes (as in the Zoobank example) have advantages if you need to create identifiers on devices that are not connected to a central instance (e. g. for mobile field recordings). In this case it is however possible to still avoid them, by using them only for a field collectors number, but not for the final accession number. Another advantage of UUIDs is that misreading one or two letters of the code will usually be detected (creation is non-sequential, well distributed, and only a tiny portion of the codes will ever be used in a given institution). The disadvantages that come with the length are the mirror image of the advantages of short codes above.
* '''#hash''': This is necessary for the Semantic web when using the “hash-method” to distinguish between the abstract concept or concrete object (e.g. '''Formica rufa''' or a specific physical specimen, which cannot be transmitted through the internet, but described) and the web pages (html, pdf, rdf-data).
*: The URI containing the hash must always refer to the abstract concept of physical object which, unlike the information resource, cannot be transmitted through the internet.


==Examples of words or strings to use in the parts of the URI pattern above==

For the subdomain and the path at least two strings are needed, with the hash method another one after the "#". The choice of words or strings does not depend on technical or stability criteria, but largely on social considerations.

Widely used terms may be sorted into these categories:
* Generic terms like: "resource", "portal", "content", "object", "concept", "thing", "topic", "citable". NOTE: ADDITIONAL PROPOSAL WELCOME!
* Terms for classes of objects or concepts like: "taxon"/"taxa", "taxonconcept", "name", "term", "sample", "specimen", "treatment", "description", "morphology", "collection", "person"/"people", "organisation"/"institution", "locality", "herbarium".
* An indicator of stability like "stable", "permanent", "permalink", "stable-id", "purl" (= permanent URL). NOTE: ADDITIONAL PROPOSAL WELCOME!
* Terms expressing only the already known fact, that this is about identifiers (which is redundant, but at the same time an advantage if one is seeking words with no relevant semantics): "id", "identifier", "guid".
* Other terms with no or reduced semantic like: "dx", "zb" (e.g. abbreviation of Zoobank), "res", "it", "o", "t", "s", "p".

Recommendations:

1. Most humans find repetitions like http://object.example.org/object/123#object or concatenations of closely overlapping terms like http://object.example.org/concept/123#topic confusing.

2. In the semantic web, the word "data" should be avoided where referring to the concept or thing itself (as opposed to the data about it). A URI like data.organisation.org/specimen/123 for a specimen itself (but redirected to another URI when the data are being returned) is easily misinterpreted as referring to the data rather than the object.

3. In principle, a similar concern may be raised over the use of "id" or "identifier" (the semantic web would speak about the thing by means of an identifier, not about the identifier), but these concerns are probably negligible.

4. Terms from the categories above can probably used interchangeably for subdomain and path, i.e. specimen.example.org/object/123 and object.example.org/specimen/123 work similarly well.
: If you foresee that operations for different objects classes may in the future be consolidated within different consortia, it may be desirable to put the object class (like specimen) in the subdomain.

5. For the hash tag to indicate that the URI with hash is the real thing, the one without the data, the choices are more limited. Examples:
: specimen.example.org/res/123#specimen
: specimen.example.org/res/123#object
: specimen.example.org/res/123#obj
: specimen.example.org/res/123#id
: specimen.example.org/res/123#itself
: PLEASE ADD YOUR EXAMPLES!
: (The above applies only to the hash method, not 303 redirection, see [[Background: Hash versus 303 redirection method|here]])

Examples:
: http://object.example.org/res/123#specimen
: http://specimen.example.org/stable-id/123#physical
: http://id.example.org/specimen/123#obj
: http://res.example.org/specimen/123#id
: http://permanent.example.org/specimen/123#id

==YOUR Preferred pattern for specimen or scientific names==

Please note that some of the URIs given in this section are examples which do not refer to existing (data) objects.

Gregor Hagedorn:
* object at <nowiki>http://specimen.example.org/permanent/123#obj</nowiki>
* rdf/html at <nowiki>http://specimen.example.org/permanent/123</nowiki>

Falko Glöckler: The Museum für Naturkunde Berlin will use
* object at <nowiki>http://coll.mfn-berlin.org/u/ZMB_123</nowiki>
* rdf at <nowiki>http://coll.mfn-berlin.org/u/ZMB_123.rdf</nowiki>
* json at <nowiki>http://coll.mfn-berlin.org/u/ZMB_123.json</nowiki>
* xml at <nowiki>http://coll.mfn-berlin.org/u/ZMB_123.xml</nowiki>
* turtle at <nowiki>http://coll.mfn-berlin.org/u/ZMB_123.turtle</nowiki>
* html at <nowiki>http://coll.mfn-berlin.org/u/ZMB_123.html</nowiki>
*: Note: the URI is constrained by the need to keep it short to be able to use a small QR-code model for tiny labels. Else we would have preferred to not abbreviate collection to coll or unit to u.

For images we will use:
* media itself at, e.g.
**<nowiki>http://media.mfn-berlin.org/u/ZMB_123__dorsal.jpg</nowiki>
**<nowiki>http://media.mfn-berlin.org/u/ZMB_123__frontal_1.dng</nowiki>
**<nowiki>http://media.mfn-berlin.org/u/ZMB_123__dorsal.png</nowiki>
* rdf metadata at <nowiki>http://media.mfn-berlin.org/u/ZMB_123__dorsal.rdf</nowiki>
* html (media context page with human readable metadata plus - where possible embedded - media item at <nowiki>http://media.mfn-berlin.org/u/ZMB_123__dorsal.html</nowiki>
*: Note: The pattern above assumes that media that are present in different mime types are always converted from each other, and that no accidental id conflict exists such that ZMB_123__dorsal.jpg and ZMB_123__dorsal.png are actually referring to different abstract "works" (e.g. by different photographers).
*: Note: Media may have complex relations. For images some of these facets are:
*:* A single specimen may be present in different views (standard like frontal, dorsal, ventral, or non-standard one)
*:* The same view of one specimen may be present with different focus, or captured by different photographer. Focus series used to create stacked images may be present.
*:* A single image may be present in different media formats (dng, png, tiff, jpg) at the same resolution
*:* A single image may be present in different levels of post-capture processing (sharpened, background removed or changed, etc.)
*:* A single image may be present at different resolution (max, web, thumbs, etc.)
*: Note: All blanks (%20-characters) in media file names will be replaced by an underscore before publishing

Richard Pyle (from gplus discussion, "{UUID-identifier}" is a concrete UUID):
* object at http://zoobank.org/{UUID-identifier}
* rdf/html at http://zoobank.org/NomenclaturalAct/{UUID-identifier}

Peter DeVries:
* object at http://ocs.taxonconcept.org/ocs/0da685c9-9cdc-4dff-baf3-38d1bdbc6552
* rdf/html at http://ocs.taxonconcept.org/ocs/0da685c9-9cdc-4dff-baf3-38d1bdbc6552.html

Roger Hyam:
* object at http://data.rbge.org.uk/herb/E00435912
* rdf/html at <nowiki>http://elmer.rbge.org.uk/bgbase/vherb/bgbasevherb.php?cfg=bgbase/vherb/bgbasevherb.cfg&specimens_barcode=E00435912</nowiki>

Quentin Groom:
* object at <nowiki>http://herbariumspecimen.belgium.museum/permanent/BR5030008086350#id</nowiki>
* rdf/html at <nowiki>http://herbariumspecimen.belgium.museum/permanent/BR5030008086350</nowiki>

Terry Catapano (for Plazi treatments):
* object at <nowiki>http://treatment.plazi.org/id/503DD3E082B645B18CFE08E3C03580ED</nowiki>
* html/xml/rdf/json representations at <nowiki>http://treatment.plazi.org/id/503DD3E082B645B18CFE08E3C03580ED.[html|xml|rdf http://treatment.plazi.org/id/B6C072CF-1CA6-40C7-8396-534E91EF7FBB.rdf |json]</nowiki>

Jordan Biserkov:
* object at <code>http://'''stable'''.example.org/specimens/''7D39CAAA-4B4B-4588-A372-D4097162B1CD''#concept</code>
* rdf/html at <code>http://'''stable'''.example.org/specimens/''7D39CAAA-4B4B-4588-A372-D4097162B1CD''</code>

Anton Güntsch:
* object at http://herbarium.bgbm.org/object/BW16684010
* rdf at http://herbarium.bgbm.org/data/rdf/BW16684010
* html at http://herbarium.bgbm.org/data/page/BW16684010

Dag Endresen (prototype under development):
* Pattern: resolver + UUID [+ suffix extension, or MIME type]
* physical object at http://purl.org/nhmuio/id/41d9cbb4-4590-4265-8079-ca44d46d27c3
* redirected to the information object found at http://gbif.no/resolver/41d9cbb4-4590-4265-8079-ca44d46d27c3.[html|rdf|json|n3|txt|csv]

Brian Fisher, antweb:
* object at http://www.antweb.org/specimen/CASENT0104542
* rdf/html at (tbd)

Nicky Nicolson / Matthew Blissett, RBG Kew:
* Herbarium specimens
** Object at http://specimens.kew.org/herbarium/K000411732#object
** http://specimens.kew.org/herbarium/K000411732 redirects to HTML at present, plan is for content negotiation, overridden by appending <tt>.html</tt>, <tt>.rdf</tt>, <tt>.xml</tt> etc.
* IPNI objects
** RDF Name: http://ipni.org/urn:lsid:ipni.org:names:488179-1
** RDF Author: http://ipni.org/urn:lsid:ipni.org:authors:1-2

Matúš Kempa, IBSAS Bratislava:
* object at http://ibot.sav.sk/herbarium/object/SAV0001234
* rdf at http://ibot.sav.sk/herbarium/data/SAV0001234.rdf

YOUR NAME:
* object at
* rdf/html at


----

Further reading:
* [[Web server 303 redirection for the semantic web]]
* Roger Hyam's summary of the "Stable Identifiers for Specimens Workshop" (4th & 5th of June 2013): http://stories.rbge.org.uk/archives/3846
* Anton Güntsch's presentation on the stable URI initiative during the CETAF34 meeting in Edinburgh (10th and 11th of September 2013): [[:File:CETAF34_ISTC_Guentsch.pdf]]
* [[DOI or LOD or DOI and LOD]]?

----

List of URI patterns used within biodiversity datasets
* https://github.com/bio-guoda/preston-identifier-registry/blob/main/registry.tsv

ISTC Meeting Spring 2017 Stuttgart

2025-03-05T13:12:43Z

D.Fichtmüller: fixed link error

{{NO_TITLE}}
'''<big>''Joint CETAF Digitisation and ISTC Group Meeting, Stuttgart''</big>'''
'''<big>27-28 March 2017</big>'''

== Attendance ==
* Wouter Addink (Leiden)
* Ana Casino (CETAF)
* Simon Chagnoux (Paris)
* Johanna Eder (Stuttgart)
* Jiří Frank (Prague)
* Katarina Gatialova (Prague)
* Falko Glöckler (Berlin, MfN)
* Karsten Gödderz (CETAF)
* Peter Grobe (Bonn)
* Quentin Groom (Meise)
* Anton Güntsch (Berlin, BGBM)
* Thomas Hörnschemeyer (Frankfurt)
* Joachim Holstein (Stuttgart)
* Jana Hoffmann (Berlin, MfN)
* Ayco Holleman (Leiden)
* Jiří Kvacek (Prague)
* Patricia Mergen (Brussels / Tervuren)
* Juan Carlos Monje (Stuttgart)
* Björn Quast (Bonn)
* Dominik Röpert (Berlin, BGBM)
* Martin Stein (Copenhagen)
* Christian Steinwender (Vienna)
* Ari Taponen (Helsinki)
* Dagmar Triebel (Munich)
* Marie-Hélène Weech (London, Kew)

== Agenda ==

=== March 27 ===

''' 9:00 - 12:00 Identifiers Implementers Group '''

Expected outcome:
* Summary of progress made in 2016.
* A clear implementation plan for 2017.
* Assignment of tasks.

''' ISTC Meeting '''

{|
|-
| '''13:00''' || Welcome, introduction of participants, and adoption of agenda (Johanna Eder, Anton Güntsch)
|-
| 13:15 || Report from identifier initiative, discussion of next steps (Anton Güntsch, [[:File:ISTC_2017_Guentsch_Identifier.pdf|presentation]])
|-
| 13:45 || Report from LOD Hackathon, discussion of next steps and collaboration opportunities (Ayco Holleman, [[:File:ISTC_2017_Hollemann_LOD.pdf|presentation]])
|-
| 14:00 || Other ISTC/CETAF initiatives
|-
| || Herbadrop (Simon Chagnoux, [[:File:ISTC_2017_Chagnoux_Herbadrop.pdf|presentation]])
|-
| || BHL-E (Jiří Frank, [[:File:ISTC_2017_Frank_BHL.pdf|presentation]])
|-
| || Geo-referencing (Ayco Holleman)
|-
| 14:30 || Other developments of ISTC members
|-
| || Common name services (Christian Steinwender)
|-
| || GFBio pipelines for collection data (Dagmar Triebel, [[:File:ISTC_2017_Triebel_GFBio.pdf|presentation]])
|-
| || MNHN Collection website and 3d gallery (Simon Chagnoux)
|-
| || Collection portal developments at the Botanic Garden Meise (Quentin Groom, [[:File:ISTC_2017_Groom_Specimen-Portal.pdf|presentation]])
|-
| '''15:15''' || Coffee
|-
| 15:45 || TDWG Biodiversity Information Standards (Quentin Groom, [[:File:ISTC_2017_Groom_TDWG.pdf|presentation]])
|-
| 16:00 || DiSSCo (Wouter Addink, [[:File:ISTC_2017_Addink_DiSSCo.pdf|presentation]])
|-
| 16:20 || EU Funding opportunities (Patricia Mergen)
|-
| 16:50 || Ideas for collaboration, next meeting(s) (All)
|-
| '''17:00''' || End of (ISTC) meeting
|}

'''19:00 Dinner'''
Theaterhaus Stuttgart, Siemensstraße 11, 70469 Stuttgart, https://www.plankenhorn-stengel.de/

=== March 28 ===

'''Digitisation Working Group '''
{|
|-
| '''9:00''' || Welcome, introduction of participants, request for AOB items and adoption of agenda
|-
| '''9:15''' || CETAF Strategy & Targets (All)
|-
| || Review all 25 CETAF Targets and identify relevant targets for the Digitsation Working Group and ISTC
|-
| || Decide how to include CETAF Strategy within the Digitisation Working Group Framework & Aims
|-
| '''9:45''' || Update on SYNTHESYS digitisation (Elspeth Haston, [[:File:CETAF_DWG_Stuttgart_March_2017_SYNTHESYS3_JRA_update.pdf|presentation]])
|-
| || Communication of outputs from project
|-
| '''10:10''' || Digitisation at the Naturkundemuseum, Stuttgart (Joachim Holstein, [https://species-id.net/o/media/d/d3/Digitisation-at-SMNS_2017.pdf presentation])
|-
| '''10:30''' || Implementation of Stable IDs in the physical collection. Implications for collection workflow (Falko Glöckler, [[:File:Gloeckler_use_cases_of_stable_URIs.pdf|presentation]])
|-
| '''11:00''' || Coffee
|-
| '''11:30''' || Digitisation Resources Gap Analysis (Elspeth Haston)
|-
| || Review draft survey
|-
| || Decide on content and structure of survey and plan the schedule
|-
| '''12:20''' || CETAF Proposal for COST Action: MOBILISE (Dagmar Triebel, [https://species-id.net/o/media/7/70/COST_presentation_CETAF-DWG-2017-03-28.pdf presentation])
|-
| '''12:30''' || Ideas for collaboration, next meeting(s) (All)
|-
| '''12:45''' || AOB
|-
| '''13:00''' || End of (DWG) meeting
|}

== Minutes ==
Minutes written by Elspeth Haston and Anton Güntsch: [[:File:MinutesofthejointCETAFDigitisationGroupandISTCMeetingStuttgart27-28March2017_(1).pdf|download]]

== Logistics ==

=== Venue ===
Lecture hall of the 
Staatliches Museum für Naturkunde Stuttgart 
Museum am Löwentor 
Rosenstein 1 
70191 Stuttgart 

Next to '''station "Nordbahnhof"''' close to the entrance of the "Rosensteinpark".

=== Directions ===
http://www.naturkundemuseum-bw.de/visit/directions

=== Hotels ===

* Ibis Budget Stuttgart, Siemensstraße 28, 70469 Stuttgart, http://www.accorhotels.com/de/hotel-5441-ibis-budget-stuttgart-city-nord/index.shtml
* Motel One Stuttgart (3 options), Tel. : +49/711/218 402 00, http://www.motel-one.com/de/hotels/stuttgart/
** Heilbronnerstraße 325, 70469 Stuttgart
** Lautenschlagerstraße 14, 70173 Stuttgart
** Badstraße 20, 70372 Stuttgart
* Stadthotel Weinsberg, Grazer Straße 32, 70469 Stuttgart-Feuerbach, http://www.ows.stadthotel-weinsberg.de/x1y8858z4543721/
* Hotel Geiger, Wilhelm-Geiger-Platz, 70469 Stuttgart-Feuerbach, http://www.hotelgeiger.de/
* Hotel Rieker, Friedrichstraße 3, 70174 Stuttgart, Tel: 0711/ 221311, Fax: 0711/ 293894, http://www.hotel-stuttgart-rieker.de
* Hotel Mercure Stuttgart City Center, Heilbronner Str. 88, 70191 Stuttgart, Tel: 0711/255580, Fax : 0711/25558100, http://www.mercure.com/de/hotel-5424-mercure-hotel-stuttgart-city center/index.shtml
* Hotel Kronen-Hotel, Kronenstrasse 48, 70174 Stuttgart, Tel: 0711/ 22510, Fax: 0711/ 2251404, http://www.kronenhotel-stuttgart.de
* Hotel Unger, Kronenstraße 17, 70173 Stuttgart, Tel: 0711 20990, Fax: 0711 2099100, http://www.hotel-unger.de

ISTC QoS Workshop Copenhagen 2018

2025-03-05T13:07:34Z

D.Fichtmüller: links to local version of openmedia files

<big>19-20 June 2018 in Copenhagen</big>

= Venue =
Natural History Museum of Denmark 
Administration 
Gothersgade 130 
DK-1123 Copenhagen

= Scope =
During the first day of the workshop, participants will present existing (and planned) implementations of stable specimen identifiers (see [[CETAF Stable Identifier Guide]]). We will discuss pragmatic actions to improve the stability of individual implementations and the consistency of the entire system. Conclusions will be part of a CETAF best practice documentation providing the guideline for future implementations.

On the second day, we will focus on the interoperability of Linked Open Specimen Data between collections as well as interoperability with external resources. Expected outcomes are 1) agreed measures for improving the semantic richness of collection data and 2) agreed joint projects demonstrating the potential of specimen LOD. There will also be the opportunity for external participants to discuss interoperability between infrastructures and the role of CETAF IDs.

We ask the participants
* to '''prepare an informal presentation''' of their (existing or planned) identifier implementation, which covers 1) the software platform used, 2) the choice of data elements and standards, 3) measures ensuring stability/persistence of identifiers, and 4) your questions, and
* to '''bring ideas''' for potential smaller projects demonstrating the potential of Linked Open Collection Data.

During the workshop, we will '''jointly document our ideas and decisions''' in a Google Doc file, which will provide the basis for the minutes and best practices documentations.

= Participants =
* Anton Güntsch (BGBM)
* Jörg Holetschek (BGBM)
* Dominik Röpert (BGBM)
* Simon Chagnoux (MNHN)
* Ayco Holleman (Naturalis)
* Martin Stein (Natural History Museum of Denmark)
* Stefan Seifert (SNSB)
* Quentin Groom (Botanic Garden Meise)
* Franck Theeten (RMCA/RBINS)
* <s>Falko Glöckler</s> Jens Dobberthin (MfN)
* Alex Schmid (SGN)
* Pascal Tschudin (GBIF Switzerland)
* Fabien Fivaz (GBIF Switzerland)
* Björn Quast (ZFMK)
* Peter Grobe (ZFMK)
* Wouter Addink (Naturalis) -only day 2
* Dimitris Koureas (Naturalis) -only day 2
* Donald Hobern (GBIF) -only day 2
* Ana Casino (CETAF) - only day 2

= Draft agenda =
== Day 1 (June 19, 10:00 - 17:00): (CETAF-) internal ==
{|
|-
| '''10:00''' || Welcome, introduction of participants, structure of the workshop, expected outcomes, minutes & documentation
|-
| '''10:45''' || Existing and planned ID implementations (<= 12 minutes each including questions)
|-
| || BGBM
|-
| || MNHN
|-
| || Naturalis
|-
| || NHM Denmark
|-
| || SNSB
|-
| || ZFMK
|-
| || BG Meise
|-
| || RMCA/RBINS
|-
| || MfN
|-
| || GBIF Switzerland
|-
| || SGN
|-
| '''13:00''' || Lunch break
|-
| '''14:00''' || Towards improved stability
|-
| || Local measures for stability of services and ID persistence?
|-
| || A central service for checking URIs?
|-
| || How can we implement an index of existing IDs?
|-
| || Do we need a machine readable registry of ID implementations?
|-
| '''15:00''' || Towards improved interoperability
|-
| || How can we agree and implement more consistent (RDF) element sets? (see [[CSPP]])
|-
| || Pragmatic approaches to semantic enrichment of collection data (e.g. at BG Meise and BGBM)
|-
| || Potential target elements for semantic enrichment?
|-
| || Potential external resources for semantic enrichment?
|-
| || Would it make sense to organise semantic enrichment with shared resources?
|-
| '''16:00''' || Questions / AOB
|-
| '''17:00''' || End of day 1
|}

'''19:00 Dinner'''
 RizRaz
 Kompagnistræde 20
 1208 Copenhagen

== Day 2 (June 20, 9:00 - 16:00): open for external participants ==
{|
|-
| '''9:00''' || Welcome, introduction of participants, structure of the workshop, expected outcomes, minutes & documentation

|-
| '''9:15''' || Linked Open Collection Data - pilot projects
|-
| || (informal) Presentation of ideas
|-
| || Discussion
|-
| || Selection of 2-3 most promising/attractive project ideas to be further developed in break out groups

|-
| '''10:00''' || Break out groups. Each group to discuss
|-
| || Scope of the pilot
|-
| || Required collections
|-
| || Required external resources
|-
| || Required semantic enrichment activities
|-
| || Assessment of feasibility
|-
| '''11:30''' || Presentation of results, discussion and selection of most attractive project(s), roadmap
|-
| '''12:30''' || Lunch break

|-
| '''13:30''' || CETAF-IDs and biodiversity informatics infrastructures
|-
| || The "data museum" project (Simon Chagnoux)
|-
| || Semantic Morph∙D∙Base - Towards Linked Open Data for Morphology (Peter Grobe)
|-
| || Unified indexing of biodiversity data (Donald Hobern)
|-
| || DiSSCo (Wouter Addink)
|-
| || Disscussion: Priorities and next steps? How can we improve coordination between infrastructures?

|-
| '''15:30''' || AOB and wrap up
|-
| '''16:00''' || End of workshop
|}

= Logistics =
== Transport ==
=== By public transport to Nørreport Station ===
The venue is in close proximity (ca. 3 minutes walk) to Nørreport Station, the main hub of public transport in Copenhagen. The next crossing is Nørre Voldgade/Gothersgade, with the Botanical Garden's main entrance at the facing corner.

=== From the airport ===
The the metro from the airport (Terminal 3) to Nørreport Station (ca. 15 minutes; there are only two metro routes, both will go to Nørreport Station). You will need a ticket valid for three zones (DKK 36.00). For guidance from Nørreport Station.
Taxi from the airport to Gothersgade 130 (ca. 25 minutes) will cost about DKK 250.

=== By train ===
Many trains will go directly to Nørreport Station. If yours doesn't, take bus **5C** headed for **Husum Torv** or **Herlev Hospital** or S-Train **A** headed for **Farum St.** from Copenhagen Central Station (Hovedbanegården) to Nørreport Station. Busses will go roughly every 5 minutes, the S-Train every 10-15 minutes. You will need a ticket valid for two zones (DKK 24.00).

A useful route planner for public transport is: https://www.rejseplanen.dk/webapp/index.html?language=en_EN

== Map ==
[[File:ISTC_DWG_2018_Map.png]]

== Hotels ==
'''Hotel Arthur''' (http://www.arthurhotels.dk/hotel-kong-arthur/) ca. DKK 1000/night 
'''Ibsens Hotel''' (http://www.arthurhotels.dk/ibsens-hotel/) ca. DKK 850/night 
'''Hotel Christian''' IV (https://www.hotelchristianiv.dk/en/) ca. DKK 900/night 
'''Hotel Nora''' (http://www.hotelnora.dk) ca. DKK 900/night 

There is good public transport in Copenhagen, and the venue is close to Nørreport Station, so it should be relatively easy to get to the meeting form hotels farther away.

ISTC Meeting Spring 2017 Stuttgart

2025-03-05T13:06:16Z

D.Fichtmüller: fixed link error

{{NO_TITLE}}
'''<big>''Joint CETAF Digitisation and ISTC Group Meeting, Stuttgart''</big>'''
'''<big>27-28 March 2017</big>'''

== Attendance ==
* Wouter Addink (Leiden)
* Ana Casino (CETAF)
* Simon Chagnoux (Paris)
* Johanna Eder (Stuttgart)
* Jiří Frank (Prague)
* Katarina Gatialova (Prague)
* Falko Glöckler (Berlin, MfN)
* Karsten Gödderz (CETAF)
* Peter Grobe (Bonn)
* Quentin Groom (Meise)
* Anton Güntsch (Berlin, BGBM)
* Thomas Hörnschemeyer (Frankfurt)
* Joachim Holstein (Stuttgart)
* Jana Hoffmann (Berlin, MfN)
* Ayco Holleman (Leiden)
* Jiří Kvacek (Prague)
* Patricia Mergen (Brussels / Tervuren)
* Juan Carlos Monje (Stuttgart)
* Björn Quast (Bonn)
* Dominik Röpert (Berlin, BGBM)
* Martin Stein (Copenhagen)
* Christian Steinwender (Vienna)
* Ari Taponen (Helsinki)
* Dagmar Triebel (Munich)
* Marie-Hélène Weech (London, Kew)

== Agenda ==

=== March 27 ===

''' 9:00 - 12:00 Identifiers Implementers Group '''

Expected outcome:
* Summary of progress made in 2016.
* A clear implementation plan for 2017.
* Assignment of tasks.

''' ISTC Meeting '''

{|
|-
| '''13:00''' || Welcome, introduction of participants, and adoption of agenda (Johanna Eder, Anton Güntsch)
|-
| 13:15 || Report from identifier initiative, discussion of next steps (Anton Güntsch, [[:File:ISTC_2017_Guentsch_Identifier.pdf|presentation]])
|-
| 13:45 || Report from LOD Hackathon, discussion of next steps and collaboration opportunities (Ayco Holleman, [[:File:ISTC_2017_Hollemann_LOD.pdf|presentation]])
|-
| 14:00 || Other ISTC/CETAF initiatives
|-
| || Herbadrop (Simon Chagnoux, [[:File:ISTC_2017_Chagnoux_Herbadrop.pdf|presentation]])
|-
| || BHL-E (Jiří Frank, [[:File:ISTC_2017_Frank_BHL.pdf|presentation]])
|-
| || Geo-referencing (Ayco Holleman)
|-
| 14:30 || Other developments of ISTC members
|-
| || Common name services (Christian Steinwender)
|-
| || GFBio pipelines for collection data (Dagmar Triebel, [[:File:ISTC_2017_Triebel_GFBio.pdf|presentation]])
|-
| || MNHN Collection website and 3d gallery (Simon Chagnoux)
|-
| || Collection portal developments at the Botanic Garden Meise (Quentin Groom, [[:File:ISTC_2017_Groom_Specimen-Portal.pdf|presentation]])
|-
| '''15:15''' || Coffee
|-
| 15:45 || TDWG Biodiversity Information Standards (Quentin Groom, [[:File:ISTC_2017_Groom_TDWG.pdf|presentation]])
|-
| 16:00 || DiSSCo (Wouter Addink, [[:File:ISTC_2017_Addink_DiSSCo.pdf|presentation]])
|-
| 16:20 || EU Funding opportunities (Patricia Mergen)
|-
| 16:50 || Ideas for collaboration, next meeting(s) (All)
|-
| '''17:00''' || End of (ISTC) meeting
|}

'''19:00 Dinner'''
Theaterhaus Stuttgart, Siemensstraße 11, 70469 Stuttgart, https://www.plankenhorn-stengel.de/

=== March 28 ===

'''Digitisation Working Group '''
{|
|-
| '''9:00''' || Welcome, introduction of participants, request for AOB items and adoption of agenda
|-
| '''9:15''' || CETAF Strategy & Targets (All)
|-
| || Review all 25 CETAF Targets and identify relevant targets for the Digitsation Working Group and ISTC
|-
| || Decide how to include CETAF Strategy within the Digitisation Working Group Framework & Aims
|-
| '''9:45''' || Update on SYNTHESYS digitisation (Elspeth Haston, [[:File:CETAF_DWG_Stuttgart_March_2017_SYNTHESYS3_JRA_update.pdf|presentation]])
|-
| || Communication of outputs from project
|-
| '''10:10''' || Digitisation at the Naturkundemuseum, Stuttgart (Joachim Holstein, [http://species-id.net/o/media/d/d3/Digitisation-at-SMNS_2017.pdf presentation])
|-
| '''10:30''' || Implementation of Stable IDs in the physical collection. Implications for collection workflow (Falko Glöckler, [[:File:Gloeckler_use_cases_of_stable_URIs.pdf|presentation]])
|-
| '''11:00''' || Coffee
|-
| '''11:30''' || Digitisation Resources Gap Analysis (Elspeth Haston)
|-
| || Review draft survey
|-
| || Decide on content and structure of survey and plan the schedule
|-
| '''12:20''' || CETAF Proposal for COST Action: MOBILISE (Dagmar Triebel, [http://species-id.net/o/media/7/70/COST_presentation_CETAF-DWG-2017-03-28.pdf presentation])
|-
| '''12:30''' || Ideas for collaboration, next meeting(s) (All)
|-
| '''12:45''' || AOB
|-
| '''13:00''' || End of (DWG) meeting
|}

== Minutes ==
Minutes written by Elspeth Haston and Anton Güntsch: [[:File:MinutesofthejointCETAFDigitisationGroupandISTCMeetingStuttgart27-28March2017_(1).pdf|download]]

== Logistics ==

=== Venue ===
Lecture hall of the 
Staatliches Museum für Naturkunde Stuttgart 
Museum am Löwentor 
Rosenstein 1 
70191 Stuttgart 

Next to '''station "Nordbahnhof"''' close to the entrance of the "Rosensteinpark".

=== Directions ===
http://www.naturkundemuseum-bw.de/visit/directions

=== Hotels ===

* Ibis Budget Stuttgart, Siemensstraße 28, 70469 Stuttgart, http://www.accorhotels.com/de/hotel-5441-ibis-budget-stuttgart-city-nord/index.shtml
* Motel One Stuttgart (3 options), Tel. : +49/711/218 402 00, http://www.motel-one.com/de/hotels/stuttgart/
** Heilbronnerstraße 325, 70469 Stuttgart
** Lautenschlagerstraße 14, 70173 Stuttgart
** Badstraße 20, 70372 Stuttgart
* Stadthotel Weinsberg, Grazer Straße 32, 70469 Stuttgart-Feuerbach, http://www.ows.stadthotel-weinsberg.de/x1y8858z4543721/
* Hotel Geiger, Wilhelm-Geiger-Platz, 70469 Stuttgart-Feuerbach, http://www.hotelgeiger.de/
* Hotel Rieker, Friedrichstraße 3, 70174 Stuttgart, Tel: 0711/ 221311, Fax: 0711/ 293894, http://www.hotel-stuttgart-rieker.de
* Hotel Mercure Stuttgart City Center, Heilbronner Str. 88, 70191 Stuttgart, Tel: 0711/255580, Fax : 0711/25558100, http://www.mercure.com/de/hotel-5424-mercure-hotel-stuttgart-city center/index.shtml
* Hotel Kronen-Hotel, Kronenstrasse 48, 70174 Stuttgart, Tel: 0711/ 22510, Fax: 0711/ 2251404, http://www.kronenhotel-stuttgart.de
* Hotel Unger, Kronenstraße 17, 70173 Stuttgart, Tel: 0711 20990, Fax: 0711 2099100, http://www.hotel-unger.de

ISTC Meeting Spring 2017 Stuttgart

2025-03-05T13:05:45Z

D.Fichtmüller: links to local version of openmedia files

{{NO_TITLE}}
'''<big>''Joint CETAF Digitisation and ISTC Group Meeting, Stuttgart''</big>'''
'''<big>27-28 March 2017</big>'''

== Attendance ==
* Wouter Addink (Leiden)
* Ana Casino (CETAF)
* Simon Chagnoux (Paris)
* Johanna Eder (Stuttgart)
* Jiří Frank (Prague)
* Katarina Gatialova (Prague)
* Falko Glöckler (Berlin, MfN)
* Karsten Gödderz (CETAF)
* Peter Grobe (Bonn)
* Quentin Groom (Meise)
* Anton Güntsch (Berlin, BGBM)
* Thomas Hörnschemeyer (Frankfurt)
* Joachim Holstein (Stuttgart)
* Jana Hoffmann (Berlin, MfN)
* Ayco Holleman (Leiden)
* Jiří Kvacek (Prague)
* Patricia Mergen (Brussels / Tervuren)
* Juan Carlos Monje (Stuttgart)
* Björn Quast (Bonn)
* Dominik Röpert (Berlin, BGBM)
* Martin Stein (Copenhagen)
* Christian Steinwender (Vienna)
* Ari Taponen (Helsinki)
* Dagmar Triebel (Munich)
* Marie-Hélène Weech (London, Kew)

== Agenda ==

=== March 27 ===

''' 9:00 - 12:00 Identifiers Implementers Group '''

Expected outcome:
* Summary of progress made in 2016.
* A clear implementation plan for 2017.
* Assignment of tasks.

''' ISTC Meeting '''

{|
|-
| '''13:00''' || Welcome, introduction of participants, and adoption of agenda (Johanna Eder, Anton Güntsch)
|-
| 13:15 || Report from identifier initiative, discussion of next steps (Anton Güntsch, [[:File:ISTC_2017_Guentsch_Identifier.pdf|presentation]])
|-
| 13:45 || Report from LOD Hackathon, discussion of next steps and collaboration opportunities (Ayco Holleman, [[:File:ISTC_2017_Hollemann_LOD.pdf|presentation]])
|-
| 14:00 || Other ISTC/CETAF initiatives
|-
| || Herbadrop (Simon Chagnoux, [[:File:ISTC_2017_Chagnoux_Herbadrop.pdf|presentation]])
|-
| || BHL-E (Jiří Frank, [[:File:ISTC_2017_Frank_BHL.pdf|presentation]])
|-
| || Geo-referencing (Ayco Holleman)
|-
| 14:30 || Other developments of ISTC members
|-
| || Common name services (Christian Steinwender)
|-
| || GFBio pipelines for collection data (Dagmar Triebel, [[:File:ISTC_2017_Triebel_GFBio.pdf|presentation]])
|-
| || MNHN Collection website and 3d gallery (Simon Chagnoux)
|-
| || Collection portal developments at the Botanic Garden Meise (Quentin Groom, [[:File:ISTC_2017_Groom_Specimen-Portal.pdf|presentation]])
|-
| '''15:15''' || Coffee
|-
| 15:45 || TDWG Biodiversity Information Standards (Quentin Groom, [[:File:ISTC_2017_Groom_TDWG.pdf|presentation]])
|-
| 16:00 || DiSSCo (Wouter Addink, [[:File:ISTC_2017_Addink_DiSSCo.pdf|presentation]])
|-
| 16:20 || EU Funding opportunities (Patricia Mergen)
|-
| 16:50 || Ideas for collaboration, next meeting(s) (All)
|-
| '''17:00''' || End of (ISTC) meeting
|}

'''19:00 Dinner'''
Theaterhaus Stuttgart, Siemensstraße 11, 70469 Stuttgart, https://www.plankenhorn-stengel.de/

=== March 28 ===

'''Digitisation Working Group '''
{|
|-
| '''9:00''' || Welcome, introduction of participants, request for AOB items and adoption of agenda
|-
| '''9:15''' || CETAF Strategy & Targets (All)
|-
| || Review all 25 CETAF Targets and identify relevant targets for the Digitsation Working Group and ISTC
|-
| || Decide how to include CETAF Strategy within the Digitisation Working Group Framework & Aims
|-
| '''9:45''' || Update on SYNTHESYS digitisation (Elspeth Haston, [[:File:CETAF_DWG_Stuttgart_March_2017_SYNTHESYS3_JRA_update.pdf|presentation]])
|-
| || Communication of outputs from project
|-
| '''10:10''' || Digitisation at the Naturkundemuseum, Stuttgart (Joachim Holstein, [http://species-id.net/o/media/d/d3/Digitisation-at-SMNS_2017.pdf presentation])
|-
| '''10:30''' || Implementation of Stable IDs in the physical collection. Implications for collection workflow (Falko Glöckler, [[:File:Gloeckler_use_cases_of_stable_URIs.pdf|presentation]])
|-
| '''11:00''' || Coffee
|-
| '''11:30''' || Digitisation Resources Gap Analysis (Elspeth Haston)
|-
| || Review draft survey
|-
| || Decide on content and structure of survey and plan the schedule
|-
| '''12:20''' || CETAF Proposal for COST Action: MOBILISE (Dagmar Triebel, [http://species-id.net/o/media/7/70/
COST_presentation_CETAF-DWG-2017-03-28.pdf presentation])
|-
| '''12:30''' || Ideas for collaboration, next meeting(s) (All)
|-
| '''12:45''' || AOB
|-
| '''13:00''' || End of (DWG) meeting
|}

== Minutes ==
Minutes written by Elspeth Haston and Anton Güntsch: [[:File:MinutesofthejointCETAFDigitisationGroupandISTCMeetingStuttgart27-28March2017_(1).pdf|download]]

== Logistics ==

=== Venue ===
Lecture hall of the 
Staatliches Museum für Naturkunde Stuttgart 
Museum am Löwentor 
Rosenstein 1 
70191 Stuttgart 

Next to '''station "Nordbahnhof"''' close to the entrance of the "Rosensteinpark".

=== Directions ===
http://www.naturkundemuseum-bw.de/visit/directions

=== Hotels ===

* Ibis Budget Stuttgart, Siemensstraße 28, 70469 Stuttgart, http://www.accorhotels.com/de/hotel-5441-ibis-budget-stuttgart-city-nord/index.shtml
* Motel One Stuttgart (3 options), Tel. : +49/711/218 402 00, http://www.motel-one.com/de/hotels/stuttgart/
** Heilbronnerstraße 325, 70469 Stuttgart
** Lautenschlagerstraße 14, 70173 Stuttgart
** Badstraße 20, 70372 Stuttgart
* Stadthotel Weinsberg, Grazer Straße 32, 70469 Stuttgart-Feuerbach, http://www.ows.stadthotel-weinsberg.de/x1y8858z4543721/
* Hotel Geiger, Wilhelm-Geiger-Platz, 70469 Stuttgart-Feuerbach, http://www.hotelgeiger.de/
* Hotel Rieker, Friedrichstraße 3, 70174 Stuttgart, Tel: 0711/ 221311, Fax: 0711/ 293894, http://www.hotel-stuttgart-rieker.de
* Hotel Mercure Stuttgart City Center, Heilbronner Str. 88, 70191 Stuttgart, Tel: 0711/255580, Fax : 0711/25558100, http://www.mercure.com/de/hotel-5424-mercure-hotel-stuttgart-city center/index.shtml
* Hotel Kronen-Hotel, Kronenstrasse 48, 70174 Stuttgart, Tel: 0711/ 22510, Fax: 0711/ 2251404, http://www.kronenhotel-stuttgart.de
* Hotel Unger, Kronenstraße 17, 70173 Stuttgart, Tel: 0711 20990, Fax: 0711 2099100, http://www.hotel-unger.de

ISTC Meeting Spring 2016 Bratislava

2025-03-05T13:01:04Z

D.Fichtmüller: links to local version of openmedia files

{{NO_TITLE}}
'''<big>''Joint CETAF Digitisation and ISTC Group Meeting, Bratislava''</big>'''
'''<big>12 April 2016, 9:00 - 16:00</big>'''

The purpose of the workshop is to bring together members of the CETAF Digitisation Group and the CETAF Information Science and Technologie Commission in order to align activities and to identify new fields of cooperation. The workshop will follow a [[ISTC_Meeting_Spring_2016_Bratislava_CIO|meeting of the CETAF CIO group]] held on the afternoon of April 11.
== Logistics ==
=== Venue ===
Institute of Botany, Slovak Academy of Sciences, Dúbravská cesta 9, Bratislava, Slovakia 
GPS: 48.17289° N, 17.0665° E 
Ground floor meeting room 
5th floor meeting room - for smaller groups 
[http://ibot.sav.sk/en/contact/bratislava/ How to get there] 
[[File:Map_Bratislava_ISTC.jpg|thumb|Walk from the bus stop to the Institute of Botany]]

=== Hotel ===
The [http://www.hotelmatysak.sk/home/ Hotel Matyšák] is close to the venue and has a direct bus connection. Otherwise, guests are free to choose any hotel in the city.

=== Shuttles from the airport Vienna ===
Shuttles leave from platform 4 every 30 minutes. Line is operated by two companies - SlovakLines and Eurolines, alternating on the departure. SlovakLines go to the Bratislava bus station (GPS 48.147056° N, 17.127073°E), Eurolines stop in the city centre (GPS 48.140712° N, 17.104243°E). You can buy tickets from the driver.

=== Public transportation in Bratislava ===
http://imhd.sk/ba/public-transport 
Ticket prices: https://imhd.sk/ba/doc/en/14971/Ticket-Price-List-from-TOMORROW-1st-Nov-2015 
Tickets are available at the ticket machines or newsstands.

=== Catering ===
The Institute of Botany will host a joint dinner at Hotel Matyšák on April 11 as well as the catering for the coffee breaks. We will be having lunch at the canteen nearby in the IBM bussiness centre - Westend Gate: menu in English, vegetarian meals (ca. 5€).

== Attendance ==

* Anton Güntsch (Berlin, BGBM)
* Dominik Röpert (Berlin, BGBM)
* Gregor Hagedorn (Berlin, MfN)
* Matúš Kempa (Bratislava)
* Karol Marhold (Bratislava)
* Jakub Bělka (Prague)
* Lukáš Bělka (Prague)
* Katarína Gatialová (Prague)
* Karsten Gödderz (CETAF)
* Elspeth Haston (Edinburgh)
* David Harris (Edinburgh)
* Simon Chagnoux (Paris)
* Stuart McLellan (Paris)
* Heimo Rainer (Vienna)
* Christian Steinwender (Vienna)
* Wilfred Gerritsen (Leiden)
* Cathy Emery (Brussels)
* Ari Taponen (Helsinki)

== Agenda ==

{|
|-
| '''9:00''' || Welcome, introduction of participants, and adoption of agenda
|-
| 9:15 || Report from CIO meeting (Hagedorn)
|-
| 9:30 || Stable identifier initiative, report and discussion of next steps (Güntsch, [[File:ISTC 2016 Identifiers Guentsch.pdf|thumb|Presentation: Stable identifiers initiative, report and discussion of next steps]])
|-
| 10:15 || Dynamic use of CETAF information (Gödderz, [[File:ISTC 2016 Goedderz DynamicUse.pdf|thumb|Presentation: Dynamic use of CETAF information]])
|-
| '''10:30''' || Coffee
|-
| 10:50 || ISTC initiatives - reports and discussion of potential for collaboration
|-
| ||
* Die Herbonauten (Röpert, [[File:ISTC 2016 Roepert Herbonauten.pdf|thumb|Presentation: Die Herbonauten]])
* Herbadrop (Chagnoux, [[File:ISTC 2016 Chagnoux Herbadrop.pdf|thumb|Presentation: Herbadrop - A pilot for storing and analysing herbarium images]])
* Visions for harmonised digital collections - prerequisites, integration, migration, challenges (Rainer, [[File:ISTC 2016 Rainer DigitalCollections.pdf|thumb|Presentation: Visions for Harmonised Digital Collections]])
* Results of the geo-referencing initiative (Gerritsen, [[File:ISTC 2016 Gerritsen Georeferencing.pdf|thumb|Presentation: Draft best practices for semi-automated georeferencing]])
|-
| 11:50 || Access to digital collections and Digitisation on Demand
|-
| '''12:30''' || Lunch
|-
| 13:30 || The collaboration of the ISTC and Digitisation Working Group in mass digitisation
|-
| 14:15 || The role of the ISTC and Digitisation Working Group in developing the European Roadmap and SYNTHESYS4
|-
| 15:15 || Potential relationships with non CETAF institutes/organisations
|-
| 15:30 || Next meeting(s)
|-
| 15:45 || AOB
|-
| '''16:00''' || End of meeting
|}

== Minutes ==
[[File:ISTC DWG 2016 Minutes.pdf|thumb|Minutes of the 2016 CETAF-ISTC meeting in Bratislava.]] (presentations are linked to the agenda)

ISTC DWG Meeting Spring 2021

2025-03-05T12:58:06Z

D.Fichtmüller: links to local version of openmedia files, added link to minutes

= Joint CETAF ISTC and Digitisation Working Group Meeting, 26 April 2021 =

'''''The meeting will be held as a video conference. The meeting notes will be created jointly in a Google Doc (link in the VC chat).'''''

== Attendance ==

== Draft agenda ==

=== ISTC (10:00 - 12:30 CEST) ===
{|
|-
| 10:00 || '''Welcome''', introduction of participants, and adoption of agenda (Anton Güntsch)
|-
| 10:15 || '''Project updates'''
|-
| || GeoCASe 2.0 - The Earth Science Collections Portal (Falko Glöckler)
|-
| || Botany Pilot (Anton Güntsch) [[:File:The_Botany_Pilot.pdf|presentation]]
|-
| 10:30 || '''Semantic annotation of locality data'''
|-
| || - in Meise (Mathias Dillen) [https://docs.google.com/presentation/d/192XoNctAQhgyK0eeGFgLyuySnW3sz1gx/edit#slide=id.p1 presentation]
|-
| || - at BGBM (Dominik Röpert) [[:File:Identification_of_geographical_free_text_information_via_Openrefine.pdf|presentation]]
|-
| 10:45 || '''Dynamic map generation''' as a service : extending OGC-WMS for occurrence maps (Franck Theeten) [[:File:EDIT_Web_Service.pdf|presentation]]
|-
| 11:00 || '''Integration with DiSSCo''': What are reasonable '''first steps?''' (Wouter Addink) [[:File:Integration_with_DiSSCo.pdf|presentation]]
|-
| 12:00 || '''IIIF''': from experiment to '''infrastructure''' (Roger Hyam) [[:File:IIIF_-_Experiment_to_Infrastructure.pdf|presentation]]
|-
| 12:15 || '''AOM''', next meeting
|-
| 12:30 || '''End of meeting'''
|}

=== Lunch Break (12:30 - 13:15 CEST) ===

=== DWG (13:15 - 16:00 CEST) ===
{|
|-
| 13:15 || '''Welcome''', introduction of participants, and adoption of agenda (Elspeth Haston)
|-
| 13:30 || '''DWG Update'''
|-
| || MIDS (Elspeth Haston & Alex Hardisty)
|-
| || CETAF Digitisation Target
|-
| 14:00 || '''Project updates'''
|-
| || - CETAF Registry (Ana Casino) [[:File:CETAF_collection_registry.pdf|presentation]]
|-
| || - OpenDS (Alex Hardisty) [[:File:OpenDS_Update.pdf|presentation]]
|-
| || - Specimen Data Refinery (Laurence Livermore)
|-
| 15:00 || '''Next steps for Digitisation Working Group''' (Elspeth Haston and ALL)
|-
| 15:15 || CETAF proposal for the '''Horizon Europe call''' on developing taxonomic capacity (Ana Casino)
|-
| 15:45 || '''AOB''', next meeting
|-
| 16:00 || '''End of meeting'''
|}

== Minutes ==
[[:File:Minutes_ISTC_DWG_2021.pdf]]

ISTC DWG Meeting Spring 2018 Copenhagen

2025-03-05T12:54:37Z

D.Fichtmüller: links to local version of openmedia files

= Joint CETAF ISTC and Digitisation Working Group Meeting, Copenhagen 21-22 February 2018 =
== Attendance ==
* Quentin Groom (Meise)
* Anton Güntsch (BGBM)
* Patricia Mergen (RMCA / Meise)
* Dominik Röpert (BGBM)
* Wouter Addink (Naturalis)
* Ana Casino (CETAF)
* Karsten Gödderz (CETAF)
* Björn Quast (ZFMK)
* Falko Glöckler (MfN Berlin)
* Dagmar Triebel (SNSB)
* Ingimar Erlingsson (Swedish Museum of Natural History)
* Elspeth Haston (RBGE)
* Wilfred Gerritsen (Naturalis)
* Sarah Phillips (Kew)
* Dare Talvitie (Finnish Museum of Natural History)
* Jere Kahanpää (Finnish Museum of Natural History)
* Jiří Frank (Prague)
* Martin Soucek (Prague)
* Jörg Lange (Stuttgart)
* Simon Chagnoux (Paris)
* Heimo Rainer (Vienna)
* Christian Steinwender (Vienna)

== Agenda ==
'''February 21'''
=== ISTC (13:00 - 17:00) ===
{|
|-
| '''13:00''' || Welcome, introduction of participants, and adoption of agenda (Anton Güntsch)
|-
| 13:15 || Stable IDs - summary of activities in 2017 [discussion of next steps] (Anton Güntsch, [https://species-id.net/o/media/b/b0/ISTC_2018_Copenhagen_Guentsch_Identifier.pdf presentation])
|-
| 14:00 || The Netherlands Biodiversity API (Wilfred Gerritsen, [https://species-id.net/o/media/9/9a/ISTC_2018_Gerritsen_NBA.pdf presentation])
|-
| 14:30 || Die Herbonauten [discussion: collaboration of citizen science platforms in CETAF] (Dominik Röpert, [https://species-id.net/o/media/c/cd/ISTC_2018_Roepert_Herbonauten.pdf presentation])
|-
| 14:45 || ICEDIG (Quentin Groom, [https://species-id.net/o/media/9/93/ISTC_2018_Groom_ICEDIG.pdf presentation])
|-
| '''15:00''' || Coffee
|-
| 15:30 || other projects: IndExs - Index of Exsiccatae (Dagmar Triebel, [https://species-id.net/o/media/b/b2/ISTC_2018_Triebel_IndExs.pdf presentation])
|-
| 15:45 || other projects: MORPHYLL: A database of fossil leaves and their morphological traits (Jörg Lange, [https://species-id.net/o/media/d/d4/ISTC_2018_Lange_Morphyll.pdf presentation])
|-
| 16:00 || The CETAF Strategy and Development Plan (2015-2025) [review and discussion, see https://cetaf.org/sites/default/files/final_strategy_and_strategic_development_plan.pdf] (All)
|-
| 16:30 || DiSSCo [alignment of ISTC activities with DiSSCo] (Wouter Addink, [https://species-id.net/o/media/a/a3/ISTC_2018_Addink_DiSSCo.pdf presentation])
|-
| 16:50 || EU Opportunities (Patricia Mergen [[:File:ISTC_2018_Mergen_EU-Opportunities.pdf|presentation]])
|-
| 17:10 || SYNTHESYS+ [Overview of ISTC-related activities] (All)
|-
| 17:30 || AOB and next meeting(s) (All)
|-
| '''17:45''' || End of (ISTC) meeting
|}

'''19:00 Dinner'''
 RizRaz
 Store Kannikestræde 19
 1169 København K

'''February 22'''

=== Digitisation Working Group (9:00 - 13:00) ===

{|
|-
| '''09:00''' || Welcome, introduction of participants, and adoption of agenda (Elspeth Haston)
|-
| 09:15 || Review of digitisation based on recent surveys ()
|-
| || 1) Digitisation Resources & Gap Analysis Survey (Elspeth Haston, [[:File:Digitisation_resources_gap_analysis.pdf|presentation]])
|-
| || 2) SYNTHESYS3 State of Digitisation survey (Sarah Phillips, [[:File:Digitisation_Working_Group_syntheys_Survey.pdf|presentation]])
|-
| 10:15 || Digitisation Definition for Collections (All, [[:File:Digitisation_definitions_for_collections.pdf|presentation]])
|-
| 10:30 || The CETAF Strategy and Development Plan (2015-2025) [review and discussion, see https://cetaf.org/sites/default/files/final_strategy_and_strategic_development_plan.pdf] (All)
|-
| '''11:00''' || Coffee
|-
| 11:30 || SYNTHESYS+ continued (All)
|-
| 12:30 || AOB and next meeting(s) (All)
|-
| '''13:00''' || End of (DWG) meeting
|}

== Minutes ==
[https://species-id.net/o/media/a/aa/CETAF_ISTC_DWG_2018_Minutes_Final.pdf download (pdf)]

== Logistics ==
=== Venue ===
Natural History Museum of Denmark 
Administration 
Gothersgade 130 
DK-1123 Copenhagen

=== Transport ===
==== By public transport to Nørreport Station ====
The venue is in close proximity (ca. 3 minutes walk) to Nørreport Station, the main hub of public transport in Copenhagen. The next crossing is Nørre Voldgade/Gothersgade, with the Botanical Garden's main entrance at the facing corner.

==== From the airport ====
The the metro from the airport (Terminal 3) to Nørreport Station (ca. 15 minutes; there are only two metro routes, both will go to Nørreport Station). You will need a ticket valid for three zones (DKK 36.00). For guidance from Nørreport Station.
Taxi from the airport to Gothersgade 130 (ca. 25 minutes) will cost about DKK 250.

==== By train ====
Many trains will go directly to Nørreport Station. If yours doesn't, take bus **5C** headed for **Husum Torv** or **Herlev Hospital** or S-Train **A** headed for **Farum St.** from Copenhagen Central Station (Hovedbanegården) to Nørreport Station. Busses will go roughly every 5 minutes, the S-Train every 10-15 minutes. You will need a ticket valid for two zones (DKK 24.00).

A useful route planner for public transport is: https://www.rejseplanen.dk/webapp/index.html?language=en_EN

=== Map ===
[[:File:ISTC_DWG_2018_Map.png|Download]]

=== Hotels ===
'''Hotel Arthur''' (http://www.arthurhotels.dk/hotel-kong-arthur/) ca. DKK 1000/night 
'''Ibsens Hotel''' (http://www.arthurhotels.dk/ibsens-hotel/) ca. DKK 850/night 
'''Hotel Christian''' IV (https://www.hotelchristianiv.dk/en/) ca. DKK 900/night 
'''Hotel Nora''' (http://www.hotelnora.dk) ca. DKK 900/night 

There is good public transport in Copenhagen, and the venue is close to Nørreport Station, so it should be relatively easy to get to the meeting form hotels farther away.

ISTC DWG Meeting Spring 2019 Vienna

2025-03-05T12:20:22Z

D.Fichtmüller: links to local version of openmedia files

= Joint CETAF ISTC and Digitisation Working Group Meeting, Vienna 13-14 February 2019 =
== Attendance ==
* Anton Güntsch (BGBM Berlin)
* Elspeth Haston (RBGE)
* Heimo Rainer (Vienna)
* Dominik Röpert (BGBM Berlin)
* Peter Grobe (ZFMK)
* Björn Quast (ZFMK)
* Martin Stein (Copenhagen)
* Dagmar Triebel (SNSB)
* Mathias Dillen (Meise)
* Ayco Holleman (Naturalis)
* Alex Hardisty (Cardiff)
* Roger Hyam (RBGE)
* Falko Glöckler (MfN Berlin)
* Simon Chagnoux (Paris)
* Wouter Addink (Naturalis)
* Frederik Berger (MfN Berlin)
* Laurence Livermore (NHM)
* Celia Santos (CSIC)
* Patrik Mráz (Charles University, Prague)
* Patricia Mergen (Meise/Tervuren)
* Ana Casino (CETAF)
* Carlos Monje (SMNS Stuttgart)
* Joachim Holstein (SMNS Stuttgart)
* Karol Marhold (Bratislava)
* Xavier Vermeersch (CETAF)
* Thomas Hörnschemeyer (Senckenberg)
* Luc Willemse (Naturalis)
* Jiri Frank (NM, Prague)
* Anne Koivunen (UH, Luomus)
* Claudia Kamcke (Braunschweig)

== Draft agenda ==
'''February 13'''
=== ISTC (13:00 - 18:00) ===

{|
|-
| '''13:00''' || Welcome, introduction of participants, adoption of agenda (A. Güntsch)
|-
| 13:20 || QoS workshop Copenhagen - report, next steps
|-
| || - "Botany Pilot" (D. Röpert)
|-
| || - ID Implementers Registry (A. Güntsch, see [https://docs.google.com/spreadsheets/d/1vHl2xDghffm6HfQhVeruHV6ZAWAnrc-2LPasq0fOyF4/edit#gid=83189964 draft registry])
|-
| || - CETAF Specimen URI Tester - new developments (R. Hyam, see [http://herbal.rbge.info/ URI Tester] and [http://iiif.rbge.info/ iiiF])
|-
| || - Semantic enrichment of collector information (M. Dillen, [[:File:Sementic_enrichment_of_collector_information.pdf|presentation]])
|-
| '''14:20''' || Coffee break
|-
| 14:50 || DiSSCo Technical Infrastructure
|-
| || - Infrastructure overview (A. Hardisty)
|-
| || - Discussion (central vs distributed services?, responsibilities and role of natural history collections?, role of CETAF IDs for specimens?, joint activities?, other questions?)
|-
| 16:00 || DiSSCo related activities
|-
| || - COST Mobilise WG4 "Development of Standards and Guidelines for data archiving and long-term preservation" (D. Triebel, [https://species-id.net/o/media/7/7f/COST_Mobilise_WG4_-_Development_of_Standards_and_Guidelines_for_data_archiving_and_long-term_preservation.pdf presentation])
|-
| || - GeoCASe – current situation and next steps (F. Glöckler)
|-
| || - COST Mobilise Person ID workshop (E. Haston)
|-
| 16:45 || On the Way from Nagoya to Legal Handling of Accession Units in collections: Management of ABS codes in Diversity Workbench (P. Grobe, [[:File:On_the_Way_from_Nagoya_to_Legal_Handling_of_Accession_Units_in_collections.pdf|presentation]])
|-
| 17:00 || CETAF strategy and development plan - targets and activities
|-
| 17:45 || AOB, next meetings
|-
| '''18:00''' || End of (ISTC) meeting
|}

'''19:00 Dinner''' || [https://www.diehalle.at/ HALLE Café Restaurant] - [https://goo.gl/maps/DrDA1CnogDF2 location: Museumsplatz 1, 1070 Wien]

'''February 14'''

=== Digitisation Working Group (9:00 - 13:00) ===

{|
|-
| '''09:00''' || Welcome, introduction of participants, adoption of agenda (E Haston)
|-
| 09:15 || CETAF strategy and development plan - targets and activities (E Haston & A Güntsch)
|-
| 09:30 || Minimal Information for Digital Specimens (MIDS) (A Hardisty)
|-
| '''10:30''' || Coffee Break
|-
| 11:00 || Review of digitisation within DiSSCO-related projects and work programs
|-
| || - SYNTHESYS+ (E Haston & General Discussion)
|-
| || - ICEDIG survey results (X Vermeersch)
|-
| || - MOBILISE (E Haston & General Discussion)
|-
| 12:30 || CETAF Collections Group (C Quaisser)
|-
| 12:45 || AOB, next meetings
|-
| '''13:00''' || End of DWG meeting
|}

== Minutes ==
[[:File:Minutes_of_the_CETAF_ISTC-DWG_meeting%2C_Vienna_2019.pdf|download(pdf)]]

== Logistics ==
=== Venue ===
Natural History Museum Vienna 
Burgring 7 
AT-1010 Vienna

The venue is located just outside and opposite of subway Station VOLKSTHEATER - exit "Ring/Museen".
=== Transport ===
==== Arrival ====
==== From the airport ====
At the airport you will find green signs once getting out that lead you to a direct train connection called '''CAT (City Airport Train)'''.
It runs every 30 minutes HH:09 and HH:39 nonstop to the "Wien Mitte Landstraße" single € 11 € return € 19
https://www.cityairporttrain.com/en/home

From there continue to the Museum using the orange subway line U3 direction Ottakring towards "Volkstheater".

==== By train ====
Nowadays trains main arrival point is '''Wien Hauptbahnhof'''. From there you can use subway line U1 to Stephansplatz change for subway number U3 to Volkstheater
A second less frequent stop is Westbahnhof. From there you can directly connect to the NHM using subway U3, again to Volkstheater.

==== During Your Stay ====
==== Public transport ====
The public transport system in Vienna is dense. Tickets can be purchased at counters of bigger stations, at the airport, railway stations or online
https://shop.wienerlinien.at/index.php/tickets

A useful route planner for public transport is @ https://www.wienerlinien.at/eportal3/ep/tab.do?tabId=0
Available also as a mobile App '''QANDO''' https://m.qando.at

=== Map ===
[https://goo.gl/maps/FgBYyyVNegk View Map]
=== Hotels ===
IBIS - https://www.accorhotels.com/gb/hotel-0796-ibis-wien-mariahilf/index.shtml
MERCURE - https://www.accorhotels.com/gb/hotel-5358-hotel-mercure-wien-westbahnhof/index.shtml
LEONARDO - https://www.leonardo-hotels.com/leonardo-hotel-vienna
Pension Wild - https://www.pension-wild.com/en/

all available direct or via booking.com / Expedia / trivago etc.

ISTC DWG Meeting Spring 2020 London

2025-03-05T12:13:19Z

D.Fichtmüller: links to local version of openmedia files

= Joint CETAF ISTC and Digitisation Working Group Meeting, 21st April 2020 =

== '''''Please note that the meeting has been cancelled due to the Corona Virus in favour of a teleconference. So please save the date. The agenda will soon be communicated via the email lists of the ISTC and DWG working groups and this wiki page.''''' ==

== Attendance (please add your name) ==
* Anton Güntsch (BGBM)
* Elspeth Haston (RBGE)
* Dominik Röpert (BGBM)
* Wouter Addink (Naturalis)
* Quentin Groom (Meise)
* Mathias Dillen (Meise)
* Maarten Trekels (Meise)
* Pieter Huybrechts (Meise)
* Stefan Seifert (SNSB)
* Dagmar Triebel (SNSB)
* Wiebke Walbaum (SMNS)
* Sharif Islam (Naturalis)
* Roger Hyam (RBGE)
* Heimo Rainer (NHMW)
* Ari Taponen (Luomus)
* Patricia Mergen (Meise and RMCA)
* Agnes Wijers (Cultural Connections)
* Laurence Livermore (NHM London)
* Falko Glöckler (MfN Berlin)
* Matt Woodburn (NHM London)
* Sarah Phillips (RBGK)
* Karol Marhold (SAV)
* Ana Casino (CETAF)
* Laura Tilley (CETAF)
* Luc Willense (Naturalis)
* Jiri Frank (NMP)
* Patrik Mráz (NMP)
* Peter Grobe (ZFMK)
* Björn Quast (ZFMK)
* Jean-Marc Herpers (RMCA)
* Franck Theeten (RMCA / RBINS)
* Henry Engledow (Meise)
* Rob Turner (Kew)
* Paul Braun (MnhnL)
* Anne Koivunen (Luomus)
* Celia Santos (MNCN-CSIC)
* Pierre-Yves Gagnier (MNHN Paris)
* Fredrik Berger (MfN)
* Rob Cubey (RBGE)
* Robyn Drinkwater (RBGE)
* Sally King (RBGE)
* Sofie De Smedt (Meise)
* Alex Hardisty (Cardiff University and DiSSCo Technical Team)
* Marie-Hélène Weech (Kew)
* Josh Humphries (NHM London)

== Draft agenda ==

=== DWG (09:30 - 11:30 CEST) ===

{|
|-
| 09:30 || '''Welcome''', introduction of participants, and adoption of agenda (Elspeth Haston)
|-
| 09:45 || CETAF Strategy and '''Strategic Development Plan''' revisited (Elspeth Haston, [[CETAF Strategy ISTC DWG|Link to CETAF ISTC & DWG Actions & Targets]])
|-
| 10:00 || '''MIDS''' update (Elspeth Haston & Alex Hardisty, [[:File:ISTC-DWG_2020_Haston_Hardisty_MIDS.pdf|presentation]])
|-
| 10:15 || '''Transcription options and standards''' update (Quentin Groom, [[:File:ISTC-DWG_2020_Groom_Transcription.pdf|presentation]]) - https://academic.oup.com/database/article/doi/10.1093/database/baz129/5670756
|-
| 10:30 || '''Imaging best practice''' update from '''ICEDIG''' (Agnes Wijers)
|-
| 10:45 || '''DiSSCo Synchronisation Group 4: Digitisation''' update (Laurence Livermore)
|-
| 11:00 || '''ELViS''' update (Wouter Addink, [[:File:ISTC-DWG_2020_Addink_ELViS.pdf|presentation]])
|-
| 11:15 || '''AOB''', next meetings
|-
| 11:30 || '''Break''' for coffee, meeting room will be kept open for people to catch up with each other
|}

=== Breakout Sessions (11:45 - 12:45 CEST) ===

{|
|-
| 11:45 || '''Calculating % CETAF Collections Digitised'''. This session will run through the process of calculating the percentage of collections digitised in CETAF institutes as part of the CETAF Strategy targets. The discussion will include many of the topics covered in the DWG meeting earlier in the morning.
|}

=== ISTC (13:30 - 15:30 CEST) ===

{|
|-
| 13:30 || '''Welcome''', introduction of participants, and adoption of agenda (Anton Güntsch)
|-
| 13:45 || '''RDA''' biodiversity data integration IG & Joint TDWG RDA Taskgroups (Wouter Addink, [[:File:ISTC-DWG_2020_Addink_RDA.pdf|presentation]])
|-
| 14:00 || Brief Reports from '''Mobilise/Warsaw''' (All, please prepare short summaries!)
|-
| 14:15 || '''Data archiving''' strategies in regard to CETAF facilities and planned DiSSCo services - highlighted by COST Mobilise (Dagmar Triebel, [[:File:ISTC-DWG_2020_Triebel_Data_Archiving.pdf|presentation]])
|-
| 14:30 || Linked Open (Collection) Data: '''the Botany Pilot''' (Dominik Röpert, [[:File:ISTC-DWG_2020_Roepert_Semantic_Annotation.pdf|presentation]])
|-
| 14:45 || Unique '''identifiers for collections''' (Laura Tilley)
|-
| 15:00 || CETAF Strategy and '''Strategic Development Plan''' revisited (Anton Güntsch, see [[CETAF Strategy ISTC DWG]])
|-
| 15:20 || '''AOB''', next meetings
|-
| 15:30 || '''End''' of meeting
|}

== Minutes ==
[[:File:Minutes_CETAF_ISTC_DWG_2020.pdf]]

ISTC DWG Meeting Spring 2020 London

2025-03-05T12:07:23Z

D.Fichtmüller: links to local version of BWF pages

= Joint CETAF ISTC and Digitisation Working Group Meeting, 21st April 2020 =

== '''''Please note that the meeting has been cancelled due to the Corona Virus in favour of a teleconference. So please save the date. The agenda will soon be communicated via the email lists of the ISTC and DWG working groups and this wiki page.''''' ==

== Attendance (please add your name) ==
* Anton Güntsch (BGBM)
* Elspeth Haston (RBGE)
* Dominik Röpert (BGBM)
* Wouter Addink (Naturalis)
* Quentin Groom (Meise)
* Mathias Dillen (Meise)
* Maarten Trekels (Meise)
* Pieter Huybrechts (Meise)
* Stefan Seifert (SNSB)
* Dagmar Triebel (SNSB)
* Wiebke Walbaum (SMNS)
* Sharif Islam (Naturalis)
* Roger Hyam (RBGE)
* Heimo Rainer (NHMW)
* Ari Taponen (Luomus)
* Patricia Mergen (Meise and RMCA)
* Agnes Wijers (Cultural Connections)
* Laurence Livermore (NHM London)
* Falko Glöckler (MfN Berlin)
* Matt Woodburn (NHM London)
* Sarah Phillips (RBGK)
* Karol Marhold (SAV)
* Ana Casino (CETAF)
* Laura Tilley (CETAF)
* Luc Willense (Naturalis)
* Jiri Frank (NMP)
* Patrik Mráz (NMP)
* Peter Grobe (ZFMK)
* Björn Quast (ZFMK)
* Jean-Marc Herpers (RMCA)
* Franck Theeten (RMCA / RBINS)
* Henry Engledow (Meise)
* Rob Turner (Kew)
* Paul Braun (MnhnL)
* Anne Koivunen (Luomus)
* Celia Santos (MNCN-CSIC)
* Pierre-Yves Gagnier (MNHN Paris)
* Fredrik Berger (MfN)
* Rob Cubey (RBGE)
* Robyn Drinkwater (RBGE)
* Sally King (RBGE)
* Sofie De Smedt (Meise)
* Alex Hardisty (Cardiff University and DiSSCo Technical Team)
* Marie-Hélène Weech (Kew)
* Josh Humphries (NHM London)

== Draft agenda ==

=== DWG (09:30 - 11:30 CEST) ===

{|
|-
| 09:30 || '''Welcome''', introduction of participants, and adoption of agenda (Elspeth Haston)
|-
| 09:45 || CETAF Strategy and '''Strategic Development Plan''' revisited (Elspeth Haston, [[CETAF Strategy ISTC DWG|Link to CETAF ISTC & DWG Actions & Targets]])
|-
| 10:00 || '''MIDS''' update (Elspeth Haston & Alex Hardisty, [https://species-id.net/openmedia/File:ISTC-DWG_2020_Haston_Hardisty_MIDS.pdf presentation])
|-
| 10:15 || '''Transcription options and standards''' update (Quentin Groom, [https://species-id.net/openmedia/File:ISTC-DWG_2020_Groom_Transcription.pdf presentation]) - https://academic.oup.com/database/article/doi/10.1093/database/baz129/5670756
|-
| 10:30 || '''Imaging best practice''' update from '''ICEDIG''' (Agnes Wijers)
|-
| 10:45 || '''DiSSCo Synchronisation Group 4: Digitisation''' update (Laurence Livermore)
|-
| 11:00 || '''ELViS''' update (Wouter Addink, [https://species-id.net/openmedia/File:ISTC-DWG_2020_Addink_ELViS.pdf presentation])
|-
| 11:15 || '''AOB''', next meetings
|-
| 11:30 || '''Break''' for coffee, meeting room will be kept open for people to catch up with each other
|}

=== Breakout Sessions (11:45 - 12:45 CEST) ===

{|
|-
| 11:45 || '''Calculating % CETAF Collections Digitised'''. This session will run through the process of calculating the percentage of collections digitised in CETAF institutes as part of the CETAF Strategy targets. The discussion will include many of the topics covered in the DWG meeting earlier in the morning.
|}

=== ISTC (13:30 - 15:30 CEST) ===

{|
|-
| 13:30 || '''Welcome''', introduction of participants, and adoption of agenda (Anton Güntsch)
|-
| 13:45 || '''RDA''' biodiversity data integration IG & Joint TDWG RDA Taskgroups (Wouter Addink, [https://species-id.net/openmedia/File:ISTC-DWG_2020_Addink_RDA.pdf presentation])
|-
| 14:00 || Brief Reports from '''Mobilise/Warsaw''' (All, please prepare short summaries!)
|-
| 14:15 || '''Data archiving''' strategies in regard to CETAF facilities and planned DiSSCo services - highlighted by COST Mobilise (Dagmar Triebel, [https://species-id.net/openmedia/File:ISTC-DWG_2020_Triebel_Data_Archiving.pdf presentation])
|-
| 14:30 || Linked Open (Collection) Data: '''the Botany Pilot''' (Dominik Röpert, [https://species-id.net/openmedia/File:ISTC-DWG_2020_Roepert_Semantic_Annotation.pdf presentation])
|-
| 14:45 || Unique '''identifiers for collections''' (Laura Tilley)
|-
| 15:00 || CETAF Strategy and '''Strategic Development Plan''' revisited (Anton Güntsch, see [[CETAF Strategy ISTC DWG]])
|-
| 15:20 || '''AOB''', next meetings
|-
| 15:30 || '''End''' of meeting
|}

== Minutes ==
[[:File:Minutes_CETAF_ISTC_DWG_2020.pdf]]

ISTC QoS Workshop Copenhagen 2018

2025-03-05T12:05:27Z

D.Fichtmüller: links to local version of BWF pages

<big>19-20 June 2018 in Copenhagen</big>

= Venue =
Natural History Museum of Denmark 
Administration 
Gothersgade 130 
DK-1123 Copenhagen

= Scope =
During the first day of the workshop, participants will present existing (and planned) implementations of stable specimen identifiers (see [[CETAF Stable Identifier Guide]]). We will discuss pragmatic actions to improve the stability of individual implementations and the consistency of the entire system. Conclusions will be part of a CETAF best practice documentation providing the guideline for future implementations.

On the second day, we will focus on the interoperability of Linked Open Specimen Data between collections as well as interoperability with external resources. Expected outcomes are 1) agreed measures for improving the semantic richness of collection data and 2) agreed joint projects demonstrating the potential of specimen LOD. There will also be the opportunity for external participants to discuss interoperability between infrastructures and the role of CETAF IDs.

We ask the participants
* to '''prepare an informal presentation''' of their (existing or planned) identifier implementation, which covers 1) the software platform used, 2) the choice of data elements and standards, 3) measures ensuring stability/persistence of identifiers, and 4) your questions, and
* to '''bring ideas''' for potential smaller projects demonstrating the potential of Linked Open Collection Data.

During the workshop, we will '''jointly document our ideas and decisions''' in a Google Doc file, which will provide the basis for the minutes and best practices documentations.

= Participants =
* Anton Güntsch (BGBM)
* Jörg Holetschek (BGBM)
* Dominik Röpert (BGBM)
* Simon Chagnoux (MNHN)
* Ayco Holleman (Naturalis)
* Martin Stein (Natural History Museum of Denmark)
* Stefan Seifert (SNSB)
* Quentin Groom (Botanic Garden Meise)
* Franck Theeten (RMCA/RBINS)
* <s>Falko Glöckler</s> Jens Dobberthin (MfN)
* Alex Schmid (SGN)
* Pascal Tschudin (GBIF Switzerland)
* Fabien Fivaz (GBIF Switzerland)
* Björn Quast (ZFMK)
* Peter Grobe (ZFMK)
* Wouter Addink (Naturalis) -only day 2
* Dimitris Koureas (Naturalis) -only day 2
* Donald Hobern (GBIF) -only day 2
* Ana Casino (CETAF) - only day 2

= Draft agenda =
== Day 1 (June 19, 10:00 - 17:00): (CETAF-) internal ==
{|
|-
| '''10:00''' || Welcome, introduction of participants, structure of the workshop, expected outcomes, minutes & documentation
|-
| '''10:45''' || Existing and planned ID implementations (<= 12 minutes each including questions)
|-
| || BGBM
|-
| || MNHN
|-
| || Naturalis
|-
| || NHM Denmark
|-
| || SNSB
|-
| || ZFMK
|-
| || BG Meise
|-
| || RMCA/RBINS
|-
| || MfN
|-
| || GBIF Switzerland
|-
| || SGN
|-
| '''13:00''' || Lunch break
|-
| '''14:00''' || Towards improved stability
|-
| || Local measures for stability of services and ID persistence?
|-
| || A central service for checking URIs?
|-
| || How can we implement an index of existing IDs?
|-
| || Do we need a machine readable registry of ID implementations?
|-
| '''15:00''' || Towards improved interoperability
|-
| || How can we agree and implement more consistent (RDF) element sets? (see [[CSPP]])
|-
| || Pragmatic approaches to semantic enrichment of collection data (e.g. at BG Meise and BGBM)
|-
| || Potential target elements for semantic enrichment?
|-
| || Potential external resources for semantic enrichment?
|-
| || Would it make sense to organise semantic enrichment with shared resources?
|-
| '''16:00''' || Questions / AOB
|-
| '''17:00''' || End of day 1
|}

'''19:00 Dinner'''
 RizRaz
 Kompagnistræde 20
 1208 Copenhagen

== Day 2 (June 20, 9:00 - 16:00): open for external participants ==
{|
|-
| '''9:00''' || Welcome, introduction of participants, structure of the workshop, expected outcomes, minutes & documentation

|-
| '''9:15''' || Linked Open Collection Data - pilot projects
|-
| || (informal) Presentation of ideas
|-
| || Discussion
|-
| || Selection of 2-3 most promising/attractive project ideas to be further developed in break out groups

|-
| '''10:00''' || Break out groups. Each group to discuss
|-
| || Scope of the pilot
|-
| || Required collections
|-
| || Required external resources
|-
| || Required semantic enrichment activities
|-
| || Assessment of feasibility
|-
| '''11:30''' || Presentation of results, discussion and selection of most attractive project(s), roadmap
|-
| '''12:30''' || Lunch break

|-
| '''13:30''' || CETAF-IDs and biodiversity informatics infrastructures
|-
| || The "data museum" project (Simon Chagnoux)
|-
| || Semantic Morph∙D∙Base - Towards Linked Open Data for Morphology (Peter Grobe)
|-
| || Unified indexing of biodiversity data (Donald Hobern)
|-
| || DiSSCo (Wouter Addink)
|-
| || Disscussion: Priorities and next steps? How can we improve coordination between infrastructures?

|-
| '''15:30''' || AOB and wrap up
|-
| '''16:00''' || End of workshop
|}

= Logistics =
== Transport ==
=== By public transport to Nørreport Station ===
The venue is in close proximity (ca. 3 minutes walk) to Nørreport Station, the main hub of public transport in Copenhagen. The next crossing is Nørre Voldgade/Gothersgade, with the Botanical Garden's main entrance at the facing corner.

=== From the airport ===
The the metro from the airport (Terminal 3) to Nørreport Station (ca. 15 minutes; there are only two metro routes, both will go to Nørreport Station). You will need a ticket valid for three zones (DKK 36.00). For guidance from Nørreport Station.
Taxi from the airport to Gothersgade 130 (ca. 25 minutes) will cost about DKK 250.

=== By train ===
Many trains will go directly to Nørreport Station. If yours doesn't, take bus **5C** headed for **Husum Torv** or **Herlev Hospital** or S-Train **A** headed for **Farum St.** from Copenhagen Central Station (Hovedbanegården) to Nørreport Station. Busses will go roughly every 5 minutes, the S-Train every 10-15 minutes. You will need a ticket valid for two zones (DKK 24.00).

A useful route planner for public transport is: https://www.rejseplanen.dk/webapp/index.html?language=en_EN

== Map ==
[http://species-id.net/openmedia/File:ISTC_DWG_2018_Map.png Download]

== Hotels ==
'''Hotel Arthur''' (http://www.arthurhotels.dk/hotel-kong-arthur/) ca. DKK 1000/night 
'''Ibsens Hotel''' (http://www.arthurhotels.dk/ibsens-hotel/) ca. DKK 850/night 
'''Hotel Christian''' IV (https://www.hotelchristianiv.dk/en/) ca. DKK 900/night 
'''Hotel Nora''' (http://www.hotelnora.dk) ca. DKK 900/night 

There is good public transport in Copenhagen, and the venue is close to Nørreport Station, so it should be relatively easy to get to the meeting form hotels farther away.

Geneva meeting

2025-03-05T12:04:09Z

D.Fichtmüller: links to local version of BWF pages

= CETAF ISTC Stable Identifier Initiative - Geneva Meeting =

<big>October 12, 2015, 9:00 - 17:00

Conservatoire et Jardin botaniques de la Ville de Genève</big>

== Venue ==
Meeting rooms: La Console – 192 Rue de Lausanne, Geneva

Villa le Chêne (reception building) – in the centre of the Garden – access via the main entrance at Place Albert-Thomas (near the bus stop “Jardin botanique” and opposite the World Trade Organisation).

== Getting here ==
Bus nos. 1 & 25 (via the main station), Bus no. 28 (from the airport) – stop “Jardin botanique.”

== Participating CETAF member institutions ==
* Berlin - BGBM
* Paris
* Edinburgh
* KEW
* Berlin - MfN
* Vienna
* Stockholm
* Geneva
* ...

== Expected outcome ==
Agree on clear implementation steps to be taken by participating partners until the spring 2016 CETAF general meeting and ISTC meeting.

Potential implementation steps:
* LOD catalogue functions.
* Ensuring that biodiversity portals such as GBIF link appropriately to specimen-URIs provided by CETAF institutions.
* Improving LOD capabilities by harmonizing RDF metadata and linking out to external information resources (e.g. persons, geographic features, scientific names).
* ...

== Draft agenda ==
* Welcome / introduction /scope
* State of the play: each member summarises the state of identifier implementations in their institution (<= 5' per presentation)
* The Wallich Catalogue project: a potential target use case showing the potential of HTTP-URI identifiers for specimens (Roger Hyam).
* A tool to propagate identifiers into remote datasets (Nicky Nicolson)
* Discussion 1: can we identify and agree on targets / use cases which i) can be achieved within 6 months and ii) nicely demonstrate the potential of HTTP-URIs and LOD?
* Discussion 2: What's needed to achieve agreed target(s)?
* Discussion 3: Agree on roadmap and homework for each partner.
* Summary

= Minutes =
== Participants ==
* Dominik Röpert (Berlin - BGBM)
* Anton Güntsch (Berlin - BGBM)
* Falko Glöckner (Berlin - MfN)
* Thomas Pfuhl (Berlin - MfN)
* Roger Hyam (Edinburgh)
* Ernst Vitek (Vienna)
* Simon Chagnoux (Paris)
* Thierry Bourgoin (Paris)
* Markus Englund (Stockholm)
* Cyril Boillat (Geneva)
* Robert Braito (Geneva)
* Apologies: Nichy Nicholson (Kew)

== Updates ==
* BGBM, MNHN, RBGE, and MfN gave an update on their existing implementations of HTTP-URI identifiers.
* All implementations provide working fully functional redirection mechanisms for both human-readable and machine-readable representations of physical collection objects.
* Each of the institutions publish the identifiers prominently on their respective collection data portals.
* The BGBM demonstrated that (if properly mapped via the BioCASE provider software) the identifiers are correctly displayed on the GBIF portal. In addition the BGBM implemented a RDF-sitemap function which provides a central access point for data aggregators.
* RBGE presented the "Wallich Catalogue Project" which builds an interactive website helping researchers understand the Wallich Catalogue* and interpret the herbarium specimens Nathaniel Wallich distributed on behalf of the British East India Company between 1829 and 1847 (http://wallich.rbge.info/). The system links to specimens held by distributed collection institutions via HTTP-URIs.
* It was agreed that
** The Wallich Catalogue provides an excellent use case for demonstrating the usefullness of HTTP-URIs and Linked Open Data.
** The CETAF ISTC identifier initiative should align their activities to improve the LoD-capabilities of the Wallich Catalogue and results should be presented at the General Meeting in Budapest (May 2016).
** A minimal set of agreed (RDF) elements implemented consistently accross CETAF organisations would greatly help to facilitate preview functions in portals for example. The ISTC should make the specification of such a minimal set a priority.
** The implementation of RDF-sitemap functions is not a priority because existing DwC-Archives can be used by aggregator systems for retrieving complete lists of HTTP-URIs published by institutions.
** Mechanisms for linking out to other domains and exploiting LoD capabilities of collection data should be further explored. Promissing candidate elements for linking out to external ressources could be for example persons, countries, place names, scientifc names, literature.
** Stockholm and Geneva will move forward with the implementation of HTTP-URIs in their institutions.

== Priorities ==
* To agree on a "CETAF Specimen Preview Profile" (CSPP).
* To implement the CSPP across members of the ISTC identifier initiative.
* To register members of the ISTC identifier initiative together with links to their implementations prominently on the CETAF website.
* To demonstrate the usefulness of the CETAF identifier system using the Wallich Catalogue use case.

== Draft CETAF Specimen Preview Profile (CSPP) ==

The participants started to brainstorm on the definition of a minimal "CETAF Specimen Preview Profile". An initial list included 26 elements/concepts which were then reduced to 12 "essential" elements to be included in the CSPP:

* title (language agnostic), mandatory
* kind of material (preserved specimen, fossil specimen, etc.; will need a controled vocabulary)
* scientific name (current)
* family
* original scientific name
* collector number
* collector name
* link to "nice" webscaled image
* geo coordinates (lon/lat; WGS84)
* iso country
* collection date
* source link (URI to institition/collection/owner)

<gallery mode="packed" widths="100px" heights="100px">
File:CSPP_01.jpg|Img1
File:CSPP_02.jpg|Img1
File:CSPP_03.jpg|Img3
File:CSPP_04.jpg|Img4
File:CSPP_05.jpg|Img5
</gallery>

With the exception of the title-element, all CSPP elements are optional.

The elements which were not included are: ipen code, type status, locality (description), (gathering) country name, ipr statement, related objects, nomenclatural code, type flag, description, literature reference, collection event id, field number, locality or area, modified date. They (and others) can however be provided as additional elements.

== Roadmap until spring 2016 ==

* Precise specification of the CSPP
** Who: Roger, Anton
** When: by end of November 2015 ([[CSPP]])

* Trial implementation (both in the collections and in the Wallish catalogue)
** Who: Roger, Simon, Falko, Dominik
** When: by end of December 2015

* Role out phase
** Who: all participants of the ISTC identifier initiative
** When: by end of March 2016

* Registration page on the CETAF website
** Who: Anton, Ana
** When: by end of March 2016

* Presentation during the CETAF GM in Budapest
** Who: Anton
** When: May 2016

== Additional medium-term objectives ==
* To assess the potential of linking out from linked open (collection) data to external ressources and to try out existing LoD visualisation and analyses tools (Dominik, Falko).
* To implement monitoring components helping to ensure that redirection mechanisms etc. implemented by CETAF members work as expected.

CETAF Stable Identifier Guide

2025-03-05T12:03:33Z

D.Fichtmüller: links to local version of BWF pages

<big>'''CETAF Stable Identifier Guide'''</big>

== {{abbr|CETAF}} {{abbr|ISTC}} Stable Identifier Initiative ==

The Stable Identifiers of the Consortium of European Taxonomic Facilities (CETAF) are globally unique, consistent and reliable identifiers for specimens in natural and botanical collections. These identifiers are used in the world wide web to redirect users and systems to images, websites and metadata of the physical objects and to integrate them with the semantic web.

== How do CETAF Stable Identifier look like? ==

[[File:Stable identifier example.png|thumb|Example for the syntax of a CETAF Stable Identifier.]]
The {{abbr|CETAF}} identifier system is based on {{abbr|HTTP}}-{{abbr|URIs}} and Linked Data principles. It is simple and future-proof.
Each collection object as well as its associated information resources (e.g. multimedia, {{abbr|RDF}}, webpages) are identified by stable HTTP-URIs that will never change. The URI Syntax for the objects is chosen and maintained by the institution owning them. This flexibility is one of the main advantages of the CETAF Stable Identifier system as it allows e.g. to include branding and local scope identifiers into the CETAF Stable Identifier URI. There are however some [[Best_practices_for_stable_URIs|best practices for stable URIs]]. Examples are:

: [http://herbarium.bgbm.org/object/B100277113 http://herbarium.bgbm.org/object/B100277113]
: [http://www.botanicalcollections.be/specimen/BR0000005516339 http://www.botanicalcollections.be/specimen/BR0000005516339]
: [http://data.rbge.org.uk/herb/E00421509 http://data.rbge.org.uk/herb/E00421509]

== How are CETAF Stable Identifiers resolved? ==

[[File:Resolving-cetaf-istc stable identifiers.png|thumb|Resolving {{abbr|URI}}-based collection identifiers using standard HTTP-redirection mechanisms.]]
A CETAF Stable Identifier allows the access of information about the corresponding collection object in various ways.
If a human user tries to access a collection object by typing it’s CETAF Stable Identifier into a web-browser, he will be redirected to a human-readable representation (e.g. html web-page) of it.
If a software-system tries to access the collection object via the same identifier, it will be redirected to a machine-processable {{abbr|RDF}}-encoded metadata record. The identifier is therefore integrated with the semantic web and can also be used in other {{abbr|RDF}} representations to link to the belonging collection object.

== What can CETAF Stable Identifiers be used for? ==

As described above, CETAF Identifiers can first of all be used to redirect users and systems to images, websites and metadata of the physical objects they belong to.
They can also be used to precisely reference specimens needed in scientific studies and serve as basis for data retrieval, integration and reproducibility of data experiments.
Additionally, the stable identifiers enable new applications in the semantic web domain. An example for this is the Biology Pilot. The [https://www.bgbm.org/ Botanic Garden and Botanical Museum Berlin], [https://www.plantentuinmeise.be/en/home/ Meise Botanic Garden] and other collections annotated thousands of specimens with the [https://kiki.huh.harvard.edu/databases/botanist_index.html HUH] and [https://www.wikidata.org/wiki/Wikidata:Main_Page WikiData] IDs of their collectors. The CETAF Stable Identifiers of the annotated specimens are available on [https://www.gbif.org/ GBIF] and a server is crawling the identifiers to organize the RDF information in a Blaze Graph triple store. This graph enables us to search for specimen by their collector {{abbr|ID}} of {{abbr|HUH}} or WikiData, which is invariant to the different spelling variants the individual institutions may be using. The query will return all relevant specimens available in the joined set of specimens regardless of their origin institution. If the number of institutions using stable identifiers grows and the amount of machine readable annotations increases, this technology could be used to basically create a “google for specimens”.

== How can I implement CETAF Stable Identifiers for my collection? ==

The CETAF Stable Identifiers can be implemented in three levels. They are described in detail in [http://herbal.rbge.info/md.php?q=documentation herbal.rbge.info’s documentation].

{| class="vertical-align-top booktable"
|+ Following conditions have to be met to reach the corresponding implementation levels
! Level 1 … !! → Level 2 !! → Level 3 !!
|-
| style="width:40%" |
{{color|green|✓}} you assigned a stable URI to each object of your collection, which will be never changed and preferably follows the [[Best_practices_for_stable_URIs|best practices for stable URIs]]

{{color|green|✓}} there exists a human-readable representation (web-page) for each of your collection objects

{{color|green|✓}} a user trying to access a collection object by typing the stable URI of it into a web-browser will be redirected to the human-readable representation (web-page) of the object (you can test this by using the [http://herbal.rbge.info/search.php CETAF URI Tester])
| style="width:30%" |
{{color|green|✓}} you reached ''Level 1''

{{color|green|✓}} there exists a machine-readable RDF metadata record for each of your collection objects

{{color|green|✓}} a machine trying to access a collection object via its identifier with <code>application/rdf+xml</code> header will be redirected to the objects machine-readable RDF metadata record (you can test this by using the [http://herbal.rbge.info/search.php CETAF URI Tester])
| style="width:30%" |
{{color|green|✓}} you reached ''Level 2''

{{color|green|✓}} the machine-readable RDF metadata record of each of your collection objects encodes application specific data (e.g. is compliant to the [[CSPP|CETAF Specimen Preview Profile—CSPP]])
|}

=== HTTP vs. HTTPS versions of CETAF {{abbr|URIs}} ===

As far as the Semantic web is concerned ''<nowiki>http://xyz</nowiki>'' and ''https://xyz'' are different things because they are different {{abbr|URIs}}. The recommendation for new implementations should be just to use HTTPS. If you have only HTTP or HTTPS versions, ''or'' want to change it you should take notice of the following:

{| class="booktable"
|-
! HTTP !! HTTPS
|-
| You
* have issued ''only HTTP'' versions of CETAF URIs and want to keep it that way
* have nothing to add technically, just have the usual 303 HTTP redirect to RDF or HTML resources in place
|You
* have issued ''only HTTPS'' versions of CETAF URIs
* don’t need to resolve then HTTP if you have never issued any, because they aren’t out there to be resolved.
|-
! style="text-align:center;" colspan="2" | Want to change HTTP to HTTPS
|-
| colspan="2" | You
* have issued HTTP versions of CETAF URIs but want to change to HTTPS
* have to keep resolving with a 303 redirect to HTTPS of the RDF or HTML resources. The RDF should contain an <code>owl:sameAs</code> assertion linking the HTTP and HTTPS versions of the {{abbr|URI}}, therefore only minor configure stuff for providers and transparent for users.
* could change to telling people to cite HTTPS rather than HTTP for your specimens but it shouldn’t matter too much as these things are linked together. The recommendation would be to cite as HTTPS if you have it implemented as at some point in the future a client may refuse to trust even a redirect from an HTTP URI (which is a bit paranoid but may happen).
|}

== Publishing CETAF IDs to {{abbr|GBIF}} ==

If your institution is using CETAF IDs and yout want them (and potential Specimen RDF) to be included into the CETAF Specimen Catalogue, they need to be used as {{abbr|GUIDs}} in the specimen data fed to GBIF. As described in [[CETAF Specimen Catalogue]], the GBIF Index is used to discover CETAF IDs.
* If DarwinCore is used, the IDs must be mapped to [http://rs.tdwg.org/dwc/terms/occurrenceID occurrence ID].
* For {{abbr|ABCD}}, the concept [https://terms.tdwg.org/wiki/abcd2:UnitGUID UnitGUID] should be used.

== How can I discover specimens with CETAF IDs and corresponding Linked Open Data ({{abbr|LOD}})? ==

You can discover specimens of institutions of the Stable Identifiers Implementers Group by using the [[CETAF Specimen Catalogue]] maintained at the {{abbr|BGBM}}, which offers a web service for getting a list of valid CETAF IDs. For implementers of level 2, who provide {{abbr|RDF}} representations of their specimens, a cache triple store with a {{abbr|SPARQL}} access point will be available soon.

== What data fields or elements are recommended or standardized? ==

The [[CETAF Specimen Preview Profile (CSPP)]] is developed as a minimal set of agreed ({{abbr|RDF}}) collection metadata elements implemented consistently across {{abbr|CETAF}} organisations. Its purpose is to provide a stable resource enabling preview functions in specimen portals. The {{abbr|CSPP}} is not meant to be comprehensive, which means that Linked Open (collection) Data implementations of CETAF institutions will usually provide much richer metadata with additional RDF-elements.

== Further Questions ==

See on [[Questions, problem solutions and further discussions (Guide of best practices)]] and in general also in [[:Category: Discussion]].

== Useful Links ==

* [[Best practices for stable URIs]]
* [[CSPP|CETAF Specimen Preview Profile (CSPP)]]—A set of standard data components for data exchange
* [https://git.bgbm.org/cetaf/stableidentifiernegotiation Source code and example documents (git.bgbm.org)]
* [http://herbal.rbge.info/ CETAF URI Tester (herbal.rbge.info)]
* [[Standards_compliance_dashboard|The Standards Compliance Dashboard]] of collaborating institutions
* [[:Category: Guide for CETAF Stable Identifiers]]—Collection of pages related to this guide or handbook

== Further reading ==

<div class="hanging-indent compact-references">
''Kuzmova, I.'' ‘Pro-IBiosphere - Stable Identifiers for Specimens – A CETAF ISTC Initiative Supported by pro-IBiosphere’. ''EUBON''. 1 July 2013. URL: https://www.pro-ibiosphere.eu/news/4296_stable_identifiers_for_specimens_-_a_cetaf_istc_initiative_supported_by_pro-ibiosphere/.

''Güntsch, A.'' et al., ‘Actionable, long-term stable and semantic web compatible identifiers for access to biological collection objects’, ''Database (Oxford)'', vol. 2017; Jan. 2017. URL: https://doi.org/10.1093/database/bax003.

''Groom, Q.'' et al., ‘Stable Identifiers for Collection Specimens’, ''Nature (Correspondence)'', 546.7656 (2017), 33; URL: https://doi.org/10.1038/546033d

''Hardisty, A.'' ‘Natural Science Identifiers & CETAF Stable Identifiers’. DiSSCoTech (blog). 28 May 2020; URL:https://dissco.tech/2020/05/28/natural-science-identifiers-cetaf-stable-identifiers/.

''Hyland, B.'' et al. ‘Best Practices for Publishing Linked Data.’ World Wide Web Consortium, 9 Jan. 2014; http://www.w3.org/TR/ld-bp/.

''Wouter, A.'' ‘Identifiers for Our Institutes – GRID and ROR’, DiSSCoTech (blog), 11 April 2020; https://dissco.tech/2020/04/11/identifiers-for-our-institutes-grid-and-ror/.

''McMurry, J. A.'' et al., ‘Identifiers for the 21st century: How to design, provision, and reuse persistent identifiers to maximize utility and impact of life science data’, ''PLOS Biology'' 15(6):e2001414 June 2017; URL:  https://doi.org/10.1371/journal.pbio.2001414.

<div style="margin-top:2ex;" ></div>

Poster: [http://www.cetaf.org/sites/default/files/cetaf-istc_stable_identifiers_poster50x70.pdf CETAF stable identifiers for specimens (1.4MB, www.cetaf.org)]
</div>

== Meetings ==
* [http://stories.rbge.org.uk/archives/3846 Edinburgh Meeting (June 2013)]
* [https://web.archive.org/web/20200318235750/https://wiki.pro-ibiosphere.eu/wiki/Workshop_Berlin_1:_How_to_improve_technical_cooperation_and_interoperability_at_the_e-infrastructure_level_Minutes Joint ISTC/pro-iBiosphere workshop Berlin, October 2013 (archived version)]
* [[Geneva_meeting|Geneva Meeting (October 2015)]]
* [[ISTC_Meeting_Spring_2016_Bratislava#Minutes|Joint CETAF-ISTC / CETAF-DWG meeting (May 2016)]]
* [[ISTC_Meeting_Spring_2017_Stuttgart|Joint CETAF-ISTC / CETAF-DWG meeting (March 2017)]]
* [[IDs_and_LOD_Discussion|(Virtual) LOD Hackathon (October 2017)]]
* [[ISTC_DWG_Meeting_Spring_2018_Copenhagen|Joint CETAF-ISTC / CETAF-DWG meeting (February 2018)]]
* [[ISTC_QoS_Workshop_Copenhagen_2018|ISTC QoS Workshop Copenhagen (June 2018)]]
* [[ISTC_DWG_Meeting_Spring_2019_Vienna|Joint CETAF-ISTC / CETAF-DWG meeting (February 2019)]]

[[Category: Guide for CETAF Stable Identifiers]]