1. Project Update Open Forum January 24, 2019
Laura Cappelletti, Director of ITS
Karen Newbery, Head, Library Systems and Integration Support

2. Recognizing and being mindful about how this change affects everyone will be critical to the success of this project.
I’ve been in the Duke Libraries 23 years this year – I know many of you on a personal level and vice versa. I’ve also been through the OLE project. Being mindful of change and how it affects people is a major focus of my role in this project. I hope that the trust we’ve built over the years can have a positive affect on this project.
Check out the Bitstreams post I published last week regarding change and the transition after a change happens.

3. Work of the Business Analyst
Who
What
How
Why
Identify stakeholders
Liaison between functional and technical stakeholders
Map current/future workflows
Map current/future data flows
Create visualizations of those workflows
Develop user acceptance testing
Collect develop and share documentation
Interviews
Observation
Share visualizations
Participate in SIGs
Having a group of people designated to perform these and other tasks frees up the developers and the functional staff to continue to do their jobs.
This is the first time we’ve filled the Business Analyst role in the Libraries. This slide shows some of the general tasks a Business Analyst would perform for an organization. Our BA’s will be contacting many staff members to learn how work is performed. They’ll work on documentation if none exists and will be leaders in creating training documentation and processes.

4. Communicate Learn Trust Listen
Communicate early, often and in different formats. Recognize that info needs to be shared more than once.
Learn
Encourage continuous learning, in individual and group settings.
Trust
Listen and speak with honesty, follow through on commitments, demonstrate high integrity.
Listen
Listen actively to both spoken and body language.
The TRLN Discovery project documented design principles to lead them through that project. Duke has guiding principles. I think it’s important for the FOLIO project to have a shared set of principles that will help us with working together to achieve success. These are some of the principles we’ve discussed. A formal document will be shared after we finalize the principles we want to uphold.

5. https://wiki.duke.edu/display/LIB/FOLIO+Project
Wiki:
Where to find information on the FOLIO at Duke project Newsletter will be published on a regular basis
Newsletters and Blog:
Communication was listed as one of the biggest issues with the OLE project, and we’d like to do better. To start, we’ll be regularly publishing a newsletter on our new blog: Folio at Duke. We’ll also share documentation on our wiki as it’s developed.

6. Data Retreat
February 11, 2019
Invitees will review and discuss points such as these as we refocus the work of the Data Normalization Team.
where is data strong/standard?
where does data present challenges? 
how do we want to enhance our data in prep for BIBFRAME/Linked Data
what policies do we need?

7. Core Team Julie Brannon – Acquisitions BA
Jeff Fleming – Data Specialist
Jackie Gottlieb – Cataloging BA
Matt Harrington – Data Specialist
Erin Nettifee – Circulation BA
Karen Newbery – Project Manager
Aleph modules will break down into smaller pieces

8. Questions?
Can I log in and play? Not yet – will let you know, will request feedback, more to come
Project plan to come
Mindmeister nodes?