BIBFRAME Implementation at
University of Alberta Library
The Canadian Cohort of LD4P and Share VDE
Abigail Sparling, Adam Cohen and Ian Bigelow
NISO Webinar: Implementing Library Linked Data, November 13th, 2019
Linked Data for UAL
Building support and capacity for BIBFRAME at UAL
Institutional Support
● Vision document: Moving Forward with Linked Data at UAL
“In order to reap the benefits of full participation in the linked open data environment, UAL should continue to
take steps towards complete conversion of existing library data to linked open data. This would involve a full
transition of workflows for resource description/metadata creation to linked open data, transitioning all library
systems for resource discovery so they work with linked open data formats, and developing new workflows,
both internal and with associated vendors and partners, to support these steps.”¹
● Building linked data implementation into UAL Strategic Priorities for 2019-2020
“Work collaboratively with national and international partners to provide leadership and advance a transition
toward open linked data for libraries.” 2
1. Moving Forward with Linked Data at UAL
2. UAL Strategic Priorities 2019-20
Staffing
● Updates to expectations and job fact sheets
○ “Position must continue building expertise in current formats and standards (MARC, AACR, RDA),
while developing expertise for description in RDF and associated query languages such as
SPARQL”
○ “Works on ongoing provision of metadata to meet current needs, with an eye to new specifications
such as BIBFRAME and associated transitioning of workflows”
● New Monographs Cataloguing Specialist tied to the LD4P Cohort project
● Linked Data Librarian Resident
Training
● Ongoing review of webinar options
● Common training through LibraryJuice Certificate in XML & RDF Based Systems
● Linked data lab time sessions to collaboratively work through concepts & ideas
● Project based training (LD4P)
Experimentation and Analysis
● MARC to BIBFRAME conversions
● University of Alberta Libraries’ Linked Data Enrichment tool
Engagement with Community (examples)
● Participation and presentations at relevant conferences and meetings
● PCC URI in MARC committee
● Canadian BIBFRAME Readiness Task Force
● Canadian Linked Data Initiative
● Share Virtual Discovery Environment (Share VDE)
● Linked Data for Production Phase 2 (LD4P2)
Infrastructure
● Testing of NEOS data in a test triplestore (GraphDB) with support from
ComputeCanada
● Testing of triplestore database work via the Stardog triplestore for Share VDE
● Set up of a local “production” triplestore for NEOS data
● Share VDE provided discovery tool for testing
● Sinopia provided cataloguing module for working with BIBFRAME
Share VDE and UAL
BIBFRAME Implementation Scenarios
What is Share-VDE?
A virtual discovery platform with the structure of the BIBFRAME
data model is created to simplify the way in which that data is
consumed.
Share-VDE is a library-driven initiative to establish an effective
working environment for the use of linked data by libraries within a
global context.
Library data are enriched with additional information and
relationships, and bibliographic and authority data are reconciled and
converted into linked data.
The network of resources created is the basis for the Share-VDE Sapientia
Cluster Knowledge Base, the common authoritative source of clusters
accessible in RDF, open to the entire Share-VDE community.
Slide courtesy Michele Casalini and Share-VDE
Who is responsible for it?
Share-VDE is a collaborative endeavour based on the needs of libraries, developed by:
Casalini Libri, provider of bibliographic and authority data as
member of the Program for Cooperative Cataloguing;
@Cult, provider of ILS, Discovery tools and Semantic web
solutions for the cultural heritage sector;
influenced by the vision of the LD4P initiative;
the joint effort of the Share-VDE Advisory Council and of the
Working Groups;
with input and active participation from an international
group of research libraries.
Slide courtesy Michele Casalini and Share-VDE
Share Participation
Share VDE Full Members
Duke University
New York University
Stanford University
University of Alberta – NEOS consortium
University of Chicago
University of Michigan at Ann Arbor
University of Pennsylvania
Yale University
National Libraries
Library of Congress
National Library of Medicine
National Library of Norway
National Library of Finland
LD4P Cohort
Cornell University
Frick Art Reference Library
Harry Ransom Center
Harvard University
Northwestern University
Princeton University
UC Davis
UC San Diego
University Colorado at Boulder
University of Minnesota
University of Texas A&M
University of Washington
Share-Catalogue Institutions
Università Degli Studi di Napoli "Federico II"
Università degli Studi della Basilicata
Università Degli Studi di Napoli L'Orientale
Universita' degli Studi di Napoli Parthenope
Università del Salento
Università degli Studi di Salerno
Università degli Studi del Sannio RCost
Università degli Studi della Campania "Luigi
Vanvitelli"
Share Art
Kunsthistorisches Institut in Florenz -
Max-Planck-Institut
Central Institute of Art History
Deutsches Forum für Kunstgeschichte Paris /
Centre allemand d'histoire de l'art Paris
Biblioteca Hertziana
Share-VDE Advisory Council
The Share-VDE Advisory Council's role is to provide insight and analysis of the MARC
to BIBFRAME transformation to make recommendations for improvements based on
member library data analysis, and project documentation. The AC also provides overall
guidance to the activities of Share-VDE initiative.
There are 4 sub-committees focusing on specific areas:
● Sapientia Entity Identification Working Group
● Authority/Identifier Management Services Working Group
● Cluster Knowledge Base Editor Working Group
● User experience/User Interface Working Group
Slide courtesy Michele Casalini and Share-VDE
Share-VDE deliverables overview (1)
The catalogue of each library converted
into BIBFRAME 2.0* modelD1
Entities are reconciled in the dataset and linked to
Share-VDE project URIs of D2 for identification.
The Cluster Knowledge Base in RDF
formatD2
Available at different levels for all institutions as it
includes data from all of the participants. Entities in D2
are enriched with URIs from external sources. All variant
forms are included.
The dataset converted in BIBFRAME
2.0* with external URIs included
D3
This dataset includes a certain number of relationships
already present in the knowledge base. Works
autonomously from D2.
Linked
* Including additional vocabularies and ontologies as needed
Slide courtesy Michele Casalini and Share-VDE
Share-VDE deliverables overview (2)
The MARC21 version of D3D4
It includes all of the institution’s records enriched with
URIs.
The Share-VDE bibliographical
datasets
in RDF made available on a triplestore
D5
Constantly updated,
queryable datasets with homogeneous data.
The Share-VDE online platform
as a common discovery systemD6
Advanced discovery interface based on BIBFRAME,
offering an easy and intuitive user experience
and rich search results.
Slide courtesy Michele Casalini and Share-VDE
The Share-VDE portal
Slide courtesy Michele Casalini and Share-VDE
New User Interface design
Slide courtesy Michele Casalini and Share-VDE
Cluster Knowledge Base Editor
Linked Data for Production (LD4P)
and UAL
Linked Data for Production (LD4P)
For the past two years, Linked Data for Production has been focusing on:
● Developing standards, guidelines, and infrastructure to communally produce
metadata as linked open data
● Developing end-to-end workflows to create linked open data in a technical
services production environment
● Extending the BIBFRAME ontology to describe library resources in specialized
domains and formats
● Engaging the broader library community to ensure a sustainable and extensible
environment
LD4P Phase 2 and the LD4P Cohort
A collaborative project among four institutions (Cornell, Harvard, Stanford, and the University of Iowa) and the
Program for Cooperative Cataloging (PCC), this phase of LD4P has seven broad goals:
1. The creation of a continuously fed pool of linked data expressed in BIBFRAME-based application profiles.
2. The development of an expanded cohort of libraries (the LD4P Cohort) capable of the creation and reuse
of linked data through the creation of a cloud-based sandbox editing environment.
3. The development of policies, techniques and workflows for the automated enhancement of MARC data
with identifiers to make its conversion to linked data as clean as possible.
4. The development of policies, techniques, and workflows for the creation and reuse of linked data and its
supporting identifiers as libraries’ core metadata.
5. Better integration of library metadata and identifiers with the Web through collaboration with Wikidata.
6. The enhancement of a widely-adopted library discovery environment (Blacklight) with linked-data based
discovery techniques.
7. The orchestration of continued community collaboration through the development of an organizational
framework called LD4.
LD4P2 Cohort Membership
University of Alberta
University of California, Davis
University of California, San Diego
Casalini Libri
University of Chicago
University of Colorado
Cornell University
Duke University
Frick Art Reference Library
Harry Ransom Center
Harvard University
University of Iowa
Library of Congress
University of Michigan
University of Minnesota
National Library of Medicine
Northwestern University
PCC
University of Pennsylvania
Princeton University
Stanford University
Texas A&M University
University of Washington
Yale University
UAL LD4P Cohort Project Summary
1. Enhancement of conversion, reconciliation and enrichment processes for MARC
to BIBFRAME
2. Exploration of new forms of authority control based on URIs by utilizing MARC
and BIBFRAME data enriched with URIs
3. Conversion of Monographs Team Operations
a. Original BIBFRAME cataloguing for monograph resources. In addition, once a suitable BIBFRAME
to MARC converter is available we hope to fully transition this team to cataloguing in BIBFRAME
and bring this experience to other teams.
b. Developing and supporting BIBFRAME copy cataloguing workflows
c. Bulk loading of record sets: Our Monographs Team is heavily involved in the maintenance of large
sets of electronic resources and our goal is to explore what similar workflows with BIBFRAME data
can and will look like in a shared and/or local triplestore.
4. Community building
Affinity and Working Groups
● Profiles Working Group
● Discovery Affinity Group
● Non-Latin Script Materials Affinity Group
● Rare Materials Affinity Group
● LD4-Wikidata Affinity Group
● Ethics in Linked Data Affinity Group
● Serials Affinity Group
● Sinopia Training Task Group
Sinopia Overview
Profile Building
Credit: Corralling Bibframe Profiles: Using the BIBFRAME Profile Editor in a Shared Environment, Nancy Lorimer and Paloma Graciana Picardo, LD4 Conference, Boston, May 2019
Profile Editor
Linked Data Editor
Linked Data Editor
Coverage of QA
Example of Questioning Authority (QA) Lookups
Universal Work Identifiers in Practice!
Share VDE’s Current Role in LD4P:
Native BIBFRAME Data Creation vs. MARC Record Conversion
● Focused on creating BIBFRAME data
natively using the Sinopia linked data
editor
● Functionality to import external RDF
data, and export BIBFRAME descriptions
● Investigating copy cataloguing workflows
utilizing BIBFRAME data converted from
MARC by SVDE
● Conversion of cohort institutions’ MARC
records to BIBFRAME
● Entity clustering and management within the
Sapientia Knowledge Base for:
○ Agents
○ Places
○ Subjects
○ Bibliographic entities (Superwork, work,
etc.)
Bringing the projects together: LD4P/SHARE-VDE Data-flow diagram
Schreur, P. (2019). LD4P2 Data Flow
● Three core levels of abstraction
○ Work
○ Instance
○ Item
● Additional key concepts
○ Agents
○ Subjects
○ Events
● Consists of RDF classes and properties
○ members of a class share certain
characteristics and may have subclasses
○ properties describe characteristics of
resources as well as relationships among
resources
BIBFRAME (as you know it)
Ongoing BIBFRAME Developments
Instance
Work
SuperWork
Item Item
IFLA-LRM Share-VDEBIBFRAME
bf:hasExpression bf:expressionOf
bf:hasInstance bf:instanceOf
bf:hasItem
Instance
Work
Hub
Item Item
bf:hasExpression bf:expressionOf
bf:hasInstance bf:instanceOf
bf:hasItem
Manifestation
Expression
Work
Item Item
is realized through realizes
is embodied in embodies
is exemplified by exemplifies bf:ItemOf bf:ItemOf
Slide courtesy Anna Lionetti and Share VDE
Next steps for UAL
● Technical infrastructure
● Refining an operational BIBFRAME Editor
● MARC to BIBFRAME/BIBFRAME to MARC conversion processes
● Testing discovery (Share VDE and LD4P)
● Expanding work to include serials, special collections, etc.
● Current pain points
○ Lack of BIBFRAME to MARC convertor
○ Batch processes
○ Production environment that works with other key tools (ILL, Circ, …)
○ Processes for entity/identifier support and maintenance
○ Testing workflows with vendors
Infrastructure change can seem messy!
Lessons Learned and Key Takeaways:
● Institutional strategic support is key (technical support, staff buy-in)
● Learning happens through training and on the ground, no one is an expert in
everything (working groups, committee participation, project involvement)
● Acknowledge that during transition there won't be perfection (progress isn't
synonymous with perfection!)
● Experimentation vs implementation: Much to be defined, refined, and developed,
but we now have tools to move progressively and iteratively into production
“Never let the future disturb you. You will meet it, if you
have to, with the same weapons of reason which today arm
you against the present.”
Marcus Aurelius, Emperor of Rome, 121-180. (2002). Meditations. London: The Folio Society.
Contact Us!
ajsparli@ualberta.ca - acohen@ualberta.ca - bigelow@ualberta.ca

Sparling and Cohen "BIBFRAME Implementation at the University of Alberta Library"

  • 1.
    BIBFRAME Implementation at Universityof Alberta Library The Canadian Cohort of LD4P and Share VDE Abigail Sparling, Adam Cohen and Ian Bigelow NISO Webinar: Implementing Library Linked Data, November 13th, 2019
  • 2.
  • 3.
    Building support andcapacity for BIBFRAME at UAL Institutional Support ● Vision document: Moving Forward with Linked Data at UAL “In order to reap the benefits of full participation in the linked open data environment, UAL should continue to take steps towards complete conversion of existing library data to linked open data. This would involve a full transition of workflows for resource description/metadata creation to linked open data, transitioning all library systems for resource discovery so they work with linked open data formats, and developing new workflows, both internal and with associated vendors and partners, to support these steps.”¹ ● Building linked data implementation into UAL Strategic Priorities for 2019-2020 “Work collaboratively with national and international partners to provide leadership and advance a transition toward open linked data for libraries.” 2 1. Moving Forward with Linked Data at UAL 2. UAL Strategic Priorities 2019-20
  • 4.
    Staffing ● Updates toexpectations and job fact sheets ○ “Position must continue building expertise in current formats and standards (MARC, AACR, RDA), while developing expertise for description in RDF and associated query languages such as SPARQL” ○ “Works on ongoing provision of metadata to meet current needs, with an eye to new specifications such as BIBFRAME and associated transitioning of workflows” ● New Monographs Cataloguing Specialist tied to the LD4P Cohort project ● Linked Data Librarian Resident Training ● Ongoing review of webinar options ● Common training through LibraryJuice Certificate in XML & RDF Based Systems ● Linked data lab time sessions to collaboratively work through concepts & ideas ● Project based training (LD4P)
  • 5.
    Experimentation and Analysis ●MARC to BIBFRAME conversions ● University of Alberta Libraries’ Linked Data Enrichment tool Engagement with Community (examples) ● Participation and presentations at relevant conferences and meetings ● PCC URI in MARC committee ● Canadian BIBFRAME Readiness Task Force ● Canadian Linked Data Initiative ● Share Virtual Discovery Environment (Share VDE) ● Linked Data for Production Phase 2 (LD4P2)
  • 6.
    Infrastructure ● Testing ofNEOS data in a test triplestore (GraphDB) with support from ComputeCanada ● Testing of triplestore database work via the Stardog triplestore for Share VDE ● Set up of a local “production” triplestore for NEOS data ● Share VDE provided discovery tool for testing ● Sinopia provided cataloguing module for working with BIBFRAME
  • 7.
    Share VDE andUAL BIBFRAME Implementation Scenarios
  • 8.
    What is Share-VDE? Avirtual discovery platform with the structure of the BIBFRAME data model is created to simplify the way in which that data is consumed. Share-VDE is a library-driven initiative to establish an effective working environment for the use of linked data by libraries within a global context. Library data are enriched with additional information and relationships, and bibliographic and authority data are reconciled and converted into linked data. The network of resources created is the basis for the Share-VDE Sapientia Cluster Knowledge Base, the common authoritative source of clusters accessible in RDF, open to the entire Share-VDE community. Slide courtesy Michele Casalini and Share-VDE
  • 9.
    Who is responsiblefor it? Share-VDE is a collaborative endeavour based on the needs of libraries, developed by: Casalini Libri, provider of bibliographic and authority data as member of the Program for Cooperative Cataloguing; @Cult, provider of ILS, Discovery tools and Semantic web solutions for the cultural heritage sector; influenced by the vision of the LD4P initiative; the joint effort of the Share-VDE Advisory Council and of the Working Groups; with input and active participation from an international group of research libraries. Slide courtesy Michele Casalini and Share-VDE
  • 10.
    Share Participation Share VDEFull Members Duke University New York University Stanford University University of Alberta – NEOS consortium University of Chicago University of Michigan at Ann Arbor University of Pennsylvania Yale University National Libraries Library of Congress National Library of Medicine National Library of Norway National Library of Finland LD4P Cohort Cornell University Frick Art Reference Library Harry Ransom Center Harvard University Northwestern University Princeton University UC Davis UC San Diego University Colorado at Boulder University of Minnesota University of Texas A&M University of Washington Share-Catalogue Institutions Università Degli Studi di Napoli "Federico II" Università degli Studi della Basilicata Università Degli Studi di Napoli L'Orientale Universita' degli Studi di Napoli Parthenope Università del Salento Università degli Studi di Salerno Università degli Studi del Sannio RCost Università degli Studi della Campania "Luigi Vanvitelli" Share Art Kunsthistorisches Institut in Florenz - Max-Planck-Institut Central Institute of Art History Deutsches Forum für Kunstgeschichte Paris / Centre allemand d'histoire de l'art Paris Biblioteca Hertziana
  • 11.
    Share-VDE Advisory Council TheShare-VDE Advisory Council's role is to provide insight and analysis of the MARC to BIBFRAME transformation to make recommendations for improvements based on member library data analysis, and project documentation. The AC also provides overall guidance to the activities of Share-VDE initiative. There are 4 sub-committees focusing on specific areas: ● Sapientia Entity Identification Working Group ● Authority/Identifier Management Services Working Group ● Cluster Knowledge Base Editor Working Group ● User experience/User Interface Working Group Slide courtesy Michele Casalini and Share-VDE
  • 12.
    Share-VDE deliverables overview(1) The catalogue of each library converted into BIBFRAME 2.0* modelD1 Entities are reconciled in the dataset and linked to Share-VDE project URIs of D2 for identification. The Cluster Knowledge Base in RDF formatD2 Available at different levels for all institutions as it includes data from all of the participants. Entities in D2 are enriched with URIs from external sources. All variant forms are included. The dataset converted in BIBFRAME 2.0* with external URIs included D3 This dataset includes a certain number of relationships already present in the knowledge base. Works autonomously from D2. Linked * Including additional vocabularies and ontologies as needed Slide courtesy Michele Casalini and Share-VDE
  • 13.
    Share-VDE deliverables overview(2) The MARC21 version of D3D4 It includes all of the institution’s records enriched with URIs. The Share-VDE bibliographical datasets in RDF made available on a triplestore D5 Constantly updated, queryable datasets with homogeneous data. The Share-VDE online platform as a common discovery systemD6 Advanced discovery interface based on BIBFRAME, offering an easy and intuitive user experience and rich search results. Slide courtesy Michele Casalini and Share-VDE
  • 14.
    The Share-VDE portal Slidecourtesy Michele Casalini and Share-VDE
  • 15.
    New User Interfacedesign Slide courtesy Michele Casalini and Share-VDE
  • 16.
  • 17.
    Linked Data forProduction (LD4P) and UAL
  • 18.
    Linked Data forProduction (LD4P) For the past two years, Linked Data for Production has been focusing on: ● Developing standards, guidelines, and infrastructure to communally produce metadata as linked open data ● Developing end-to-end workflows to create linked open data in a technical services production environment ● Extending the BIBFRAME ontology to describe library resources in specialized domains and formats ● Engaging the broader library community to ensure a sustainable and extensible environment
  • 19.
    LD4P Phase 2and the LD4P Cohort A collaborative project among four institutions (Cornell, Harvard, Stanford, and the University of Iowa) and the Program for Cooperative Cataloging (PCC), this phase of LD4P has seven broad goals: 1. The creation of a continuously fed pool of linked data expressed in BIBFRAME-based application profiles. 2. The development of an expanded cohort of libraries (the LD4P Cohort) capable of the creation and reuse of linked data through the creation of a cloud-based sandbox editing environment. 3. The development of policies, techniques and workflows for the automated enhancement of MARC data with identifiers to make its conversion to linked data as clean as possible. 4. The development of policies, techniques, and workflows for the creation and reuse of linked data and its supporting identifiers as libraries’ core metadata. 5. Better integration of library metadata and identifiers with the Web through collaboration with Wikidata. 6. The enhancement of a widely-adopted library discovery environment (Blacklight) with linked-data based discovery techniques. 7. The orchestration of continued community collaboration through the development of an organizational framework called LD4.
  • 20.
    LD4P2 Cohort Membership Universityof Alberta University of California, Davis University of California, San Diego Casalini Libri University of Chicago University of Colorado Cornell University Duke University Frick Art Reference Library Harry Ransom Center Harvard University University of Iowa Library of Congress University of Michigan University of Minnesota National Library of Medicine Northwestern University PCC University of Pennsylvania Princeton University Stanford University Texas A&M University University of Washington Yale University
  • 21.
    UAL LD4P CohortProject Summary 1. Enhancement of conversion, reconciliation and enrichment processes for MARC to BIBFRAME 2. Exploration of new forms of authority control based on URIs by utilizing MARC and BIBFRAME data enriched with URIs 3. Conversion of Monographs Team Operations a. Original BIBFRAME cataloguing for monograph resources. In addition, once a suitable BIBFRAME to MARC converter is available we hope to fully transition this team to cataloguing in BIBFRAME and bring this experience to other teams. b. Developing and supporting BIBFRAME copy cataloguing workflows c. Bulk loading of record sets: Our Monographs Team is heavily involved in the maintenance of large sets of electronic resources and our goal is to explore what similar workflows with BIBFRAME data can and will look like in a shared and/or local triplestore. 4. Community building
  • 22.
    Affinity and WorkingGroups ● Profiles Working Group ● Discovery Affinity Group ● Non-Latin Script Materials Affinity Group ● Rare Materials Affinity Group ● LD4-Wikidata Affinity Group ● Ethics in Linked Data Affinity Group ● Serials Affinity Group ● Sinopia Training Task Group
  • 23.
  • 24.
    Profile Building Credit: CorrallingBibframe Profiles: Using the BIBFRAME Profile Editor in a Shared Environment, Nancy Lorimer and Paloma Graciana Picardo, LD4 Conference, Boston, May 2019
  • 25.
  • 26.
  • 27.
  • 28.
  • 29.
    Example of QuestioningAuthority (QA) Lookups Universal Work Identifiers in Practice!
  • 30.
    Share VDE’s CurrentRole in LD4P: Native BIBFRAME Data Creation vs. MARC Record Conversion ● Focused on creating BIBFRAME data natively using the Sinopia linked data editor ● Functionality to import external RDF data, and export BIBFRAME descriptions ● Investigating copy cataloguing workflows utilizing BIBFRAME data converted from MARC by SVDE ● Conversion of cohort institutions’ MARC records to BIBFRAME ● Entity clustering and management within the Sapientia Knowledge Base for: ○ Agents ○ Places ○ Subjects ○ Bibliographic entities (Superwork, work, etc.)
  • 31.
    Bringing the projectstogether: LD4P/SHARE-VDE Data-flow diagram Schreur, P. (2019). LD4P2 Data Flow
  • 32.
    ● Three corelevels of abstraction ○ Work ○ Instance ○ Item ● Additional key concepts ○ Agents ○ Subjects ○ Events ● Consists of RDF classes and properties ○ members of a class share certain characteristics and may have subclasses ○ properties describe characteristics of resources as well as relationships among resources BIBFRAME (as you know it)
  • 33.
    Ongoing BIBFRAME Developments Instance Work SuperWork ItemItem IFLA-LRM Share-VDEBIBFRAME bf:hasExpression bf:expressionOf bf:hasInstance bf:instanceOf bf:hasItem Instance Work Hub Item Item bf:hasExpression bf:expressionOf bf:hasInstance bf:instanceOf bf:hasItem Manifestation Expression Work Item Item is realized through realizes is embodied in embodies is exemplified by exemplifies bf:ItemOf bf:ItemOf Slide courtesy Anna Lionetti and Share VDE
  • 34.
    Next steps forUAL ● Technical infrastructure ● Refining an operational BIBFRAME Editor ● MARC to BIBFRAME/BIBFRAME to MARC conversion processes ● Testing discovery (Share VDE and LD4P) ● Expanding work to include serials, special collections, etc. ● Current pain points ○ Lack of BIBFRAME to MARC convertor ○ Batch processes ○ Production environment that works with other key tools (ILL, Circ, …) ○ Processes for entity/identifier support and maintenance ○ Testing workflows with vendors
  • 35.
  • 36.
    Lessons Learned andKey Takeaways: ● Institutional strategic support is key (technical support, staff buy-in) ● Learning happens through training and on the ground, no one is an expert in everything (working groups, committee participation, project involvement) ● Acknowledge that during transition there won't be perfection (progress isn't synonymous with perfection!) ● Experimentation vs implementation: Much to be defined, refined, and developed, but we now have tools to move progressively and iteratively into production
  • 37.
    “Never let thefuture disturb you. You will meet it, if you have to, with the same weapons of reason which today arm you against the present.” Marcus Aurelius, Emperor of Rome, 121-180. (2002). Meditations. London: The Folio Society. Contact Us! [email protected] - [email protected] - [email protected]