4:00 - 4:05 p.m. - Announcements (5 minutes)
The meeting minutes for the September 30th meeting are motioned for approval. Hearing no objections, the minutes are approved and will be posted.
Welcome to Zoe Tishaev – new undergraduate representative student
Welcome to Jax Nalley – new undergraduate representative student
4:05 - 4:35 p.m. - Scholars@Duke Update, Damaris Murry, Ricard Outten (20-minute presentation, 10-minute discussion)
What it is: Scholars@Duke is a research intelligence and expert-finder application that aggregates and curates’ public data on over 10,000 Duke faculty, students, and academic staff. Through Scholars@Duke, Duke University plays a key role in the international conversation around CRIS/RIMS (Current Research Information Systems/Research Information Management Systems).
Why it’s relevant: Scholars@Duke not only enables the efficient reuse of information across the institution, but it has been a catalyst in building a culture of data governance at Duke.
Minutes:
The conversation started with Damaris mentioning that the work the team does is not just centered around scholars@duke but instead the team also does other things that involve all faculty data. One of the applications Damaris mentioned is the DFAC application. The DFAC application manages faculty appointments, promotions, and tenures at Duke. The second application is Symplectic. Symplectic is a place where you can manage your publications. The third application the team works with is the faculty data repository (FDR). The FDR application is an application as the name implies a repository of faculty data. The main talking point of this conversation today was centered around scholars@duke. The scholars@duke application is comprised of three pieces, profiles, profile manager, and export tools. Damaris then went and explained in more detail those three aspects of the scholars@duke application.
First, Damaris talked about information gathering perspective resulting in:
people - 7191 faculty, 2436 students, 1141 staff, 89 affiliates
Organizations – 2 universities, 10 schools, 219 depts/divisions, 88 centers, and institutes.
Damaris gave an overview of what a profile looks like for someone at Scholars@duke. Information for someone with a scholars@duke profile includes name and title, profile picture, links to personal sites. There are also sections about Background information, Recognition, Expertise, Research, and teaching and mentoring information. Damaris mentioned that the team tries to gather all the information about faculty that may live in different parts of the university and bring it all together in a way that is consistent regardless of where faculty work.
One key point that Damaris brought up is the difference between the information that the duke public directory shows vs what scholars@duke shows. Scholars@duke shows information that is sourced from SAP, but this information is paired down the SAP organization hierarchy into the org's that are relevant for academic purposes. A display name is then attached to make this information more consumable. The duke public directory on the contrary, sources information from a financial perspective where the name of an org unit will show as the financial name of that unit. Similarly, for a student, the program name that appears for a user in the directory is different than what is shown in the scholars@duke profile for that student.
Something else that is unique to scholars@duke profile for a user is that scholars@duke allows people to describe themselves. users can also share interests in their scholars@duke profile. They can also do global scholarships. Users can display research experience, teaching experience, or another language.
Damaris then talked about the usage of google analytics to track metrics of scholars@dukeprofiles. They track different information down to school, department, and page views for a user.
Next, Damaris talked from the perspective of the Profile management feature - you can edit your information.
profile manager – The profile manager has help tags that help people understand where the data is coming from. if they need to update their info, they can get to the source to get that information updated. Users can also hide/show information when it is pulled from different sources mainly for publications and others.
There is also support for users. Users have support through power users and through profile delegates. Power users are people that reside within their units/departments that they can contact for support. There are also profile delegates that can be contacted if any information needs to be updated. Both power users and profile delegates are trained and have the information needed to assist scholars@duke users.
Regarding profile edits over time, during 2013-2014 when this was first rolled out there were more profile edits being done by delegates. Over time, however, due to training and outreach, there has been an increase in faculty profile edits.
Damaris also talked about how the team is on the alert for errors/mishaps that may happen regarding user data.
Lastly, Damaris talked about data consumers. Data consumers are those that consume all this data in different ways. There are reporting tools that let users export their data in a CV format. another feature includes the option to show the most recent publication from embed code.
There are also tableau views. There are views ranging from department level and at the school level table views. There is a tool called widgets which is being used on department sites. This helps departments to really focus on the styling of this information instead of worrying about where to keep this information. There are also integrations around Duke from my research home pages to the department's research page sites and even office news and communication.
Damaris said that what the team is doing is unique. Users have a unique experience to let users edit their own information but also pull information from various sources to let users see their information and edit as needed.
The last point Damaris touched on is about a new redesign of scholars@duke that is coming. The redesign entails a focus on the data life cycle regarding ownership of the data, making the data accessible, also thinking about the security of the data, the quality of the data, and lastly showcasing good knowledge of the data.
Q/A:
Q: Michael Greene - My assumption has been that Scholars is mostly used in the non-teaching aspects of faculty life. Do faculty use, Scholars, in ways related to their teaching? Would some type of integration with Sakai/Kits provide value to you and your students?
A: JoAnne Van Tuyl said - someway to connect people for informal connection.
Q: Steffen a Bass said - support for handling faculty activity annual report. This can help administrators from the department perspective and school perspective.
A: Damaris answered with: we had this functionality at one point. But because we didn’t see much traction in it, nor did we get feedback on it. We decided to retire that functionality.
Steffen said it was not brought up to the department level. Steffen said he would really love to have one place to keep this information up to date.
Paul Jaskot -asked about having some tagging kind of function that can aid in building communities.
Colin Rundel - the ability to link up where our course materials are and things like that. links to external works, GitHub projects. Etc.
David MacAlpine - said that scholars@duke is the easiest to work with compared to other tools that have sprung up.
4:35 - 5:05 p.m. - Digital Humanities in Art, Art History & Visual Culture, Paul Jaskot, Victoria Szabo (20 minutes presentation, 10 minutes discussion)
What it is: Celebrating 10 years, Duke’s Digital Art History & Visual Culture Research Lab (formerly Wired! Lab) is a dynamic research community of faculty, staff, and students. The Lab engages and advances critical digital methods to promote new approaches to scholarship and pedagogy in the study and interpretation of the visual arts, architecture, cultural heritage, and urban environments.
Why it’s relevant: With a recent rebrand and the launch of a new website and publication, the Duke University Digital Art History & Visual Culture Research Lab is emphasizing the public-facing mission of advancing art historical research projects that combine digital methods with cultural challenges, from the classroom to traditional and public-facing humanities scholarship.
Minutes:
Paul Jaskot started the conversation by thanking all the teams involved in this collaborative effort. Paul said that there are two aspects to this talk, one is to talk about the digital art history and visual culture research lab and the second aspect of the talk is how to think about the digital humanities aspect more broadly.
First, Paul talked about the branding of his lab. The branding went from “Wired! Digital Art History and Visual Culture” to “Duke Digital Art History and Visual Culture Research Lab”. This new branding explains where the program is at this point and where the lab is. Paul said that they like to emphasize the research aspect of the program along with the idea of trying to pitch this to a broader community of visual culture specialists as well as digital humanities specialists.
Paul highlighted three long term goals for the DAHVAC Research lab:
- large, long-term research themes that link research and thinking
- students and faculty working together on our collaborative projects.
- A team approach to learning and rethinking the ways in which we can represent historical questions in the fields of art, architectural and urban history, as well as in the collecting and display of objects.
Paul then went on to talk about three aspects of digital art which are Object, Space, Scale, along with showing examples of each.
Paul mentioned about doing more in the space of public humanities outreach. He loves mapping and about 10 years ago took a class with sophomores for GIS.
In regard to:
Objects
• The way objects are rendered.
• GIs mapping of cities but also 3D modeling
• Can also be thought of as a database. Aggregation of a certain piece of art and brings it all together in a database type of project.
• Using photography in a way to use artifacts in a physical matter.
Space
• Building duke project in bass connections. Hoping to have a demo for this.
• Distribution of space.
• Interacting with space with augmented reality. Something you interact with within a virtual environment.
• Paul mentioned that the team is moving more recently into image-based modeling.
Scale
• Scale is the biggest game-changer in terms of how to think about humanities questions. Paul said that limits the way one thinks about scale limits your ability to do one artist.
• Think of scale in terms of aggregation of buildings. Need data specialist on the data end but also on the end of the visual arts. Hope to do more with this and thinks that duke can outstand out from the competition.
Paul shared a list of the research teams involved and said that the research work in many areas from spatial modeling, mapping, and also augmented reality and agent-based modeling to databases and how to think about data sets more generally.
Paul then introduced Victoria to talk about the other aspect of the research lab.
CMAC - computational media, arts, and cultures. Combination of programs and labs that are trying to think about how new technologies are transforming the ways that we do the work that we do but to engage with those questions in critical and theoretical and philosophical and ethical ways as we apply them to questions that come up in the humanities
another lab is Duke Art, Law, and Markets Initiative (DALMI) Lab – bringing together economics, data visualization, and statistics into the understanding of the history of the art market and the creation of preferences.
DigginLAb – cyber archaeology lab led by Mauricio forte. The research is focused on edges of archeology how research is conducted and how to express it and share it with the public. The emergence lab – more interested in creative practices, computational code manifesting in installations, exhibitions, interactive experiences, but still also getting into the questions of the archive and of testimony and transformation.
Speculative Sensation Lab (S-1) – led by Mark Hansen and Mark Olson. This is a space where the theoretical and critical condition considerations coming out of literature Marxist theory post-structuralist theory are intersecting with our understanding of media and computation. sometimes manifesting and creating objects and artifacts that try to explore the technology a new way of doing research.
XR Extended Reality Studio – led by Victoria Szabo is a space created to bring together all of the shared interests in virtual reality, augmented reality, extended reality, 3D GIs systems, games, and thinking about holidays spatial and palatial and interactive systems for real and imagined worlds.
information science and studies center/lab - foundational source for these spaces and programs. highlight digital humanities space and archival elements of that space.
Copied from their last slide of the presentation as a summary of what the team does is the following:
“A community of students, staff, and faculty using technologies to explore the visual and material culture.”
Q/A:
Q: JoAnne - how do you capture that information. object capture. where are these images coming from?
A: historical images come from publicly accessible sites. metadata is embedded in the image.
Q: Ken Rogerson asked - you find that the developers respond in the same way. how large is your world for the development of things? are you guys doing it yourself?? just curious...
A: We do have questions about when to purchase commercial solutions. but we also look at open-source solutions.
Q: Tracy asked, what do you need from us to be stronger in that space? Including in the more general digital humanities space?
A: natural language processing. more support for collaboration. intermediary. a creative director. also need staff, said Paul.
Victoria said - faculty who teach in this domain. co-curricular programs that can be more formalized. we have many of our experts that are students, adjuncts, but then they leave so we must start over again.
5:05 pm - 5:30 p.m. - Duke Flu Vaccination Process Update, Charley Kneifel (15 minutes presentation, 10 minutes discussion)
What it is: Flu vaccination processes managed by Employee Occupational Health and Wellness (EOHW) have been streamlined through the use of QR codes. We will give an update on the process and provide a demo of the new process.
Why it’s relevant: The new process will be more efficient and faster for each side of the process. This is important as all Duke employees and students are required to get their annual flu vaccination. Manual aspects of our past processes were ripe for automation, which has now been achieved.
Minutes:
Challenges:
• Vaccinatees needed to use an iPad to log in or provide their information at the time of vaccination, a lot of passing of the device
• Vaccinators needed to provide the same data over and over for themselves
• Need a simple process to support peer vaccinators
• DUID has a leading 0 that is needed.
Potential Solutions:
• Enable Vaccinatees to provide information
• Fill out a survey in Qualtrics (VaxTrax infrastructure)
• Creates a secure QR code with Vaccinatee information
• Email QR code to Vaccinatee - has sensitive encrypted information in it. Scan QR code when they arrive for a shot
• You have your QR code scanned upon arrival
We can do the same thing for the vaccinators:
• Who will they give the shot to
• What arm will it be given to
• What muscle group will it be relevant to.
Implementation Challenges:
There has to be a balancing act between encryption of the QR code payload, managing access to the API's, emailing QR codes (Images and PDF), Reading QR Codes with Javascript, users with login challenges, peer vaccinations, special cases (egg allergies, high dose vaccine)
Victor showed a demo of how the process worked:
So this is related to the Flu Vaccine – the COVID system and also the 3rd booster has a different process which is being active now but it’s a different process for it to update MyChart
Back to the Demo…
(Victor is working with a development database for our demo)
He logged in and we saw the unique QR code - the vaccinator image will have a bandaidin there in the middle of the QR code.
Now we see the demo.
• Now the Vaccinatee has a standard code with no additional image it’s just a standard QR Code. Again, as a reminder in contrast the Vaccinator will have a band-aid in the middle of their QR code.
• He also proceeded to share his screen from his phone to then scan the QR Code on his computer to complete the demonstration for us. A couple of things to note that when you print out the QR code it’s going to be Black and white because it’s best for printing out
• On the phone there is a prompt so that asks you to use the Camera… for iPad’s, there is some debate on that due to the Airwatch device management required on the medical side.
• If the scan is of the wrong QR code, then the vaccinator see a red bar that it’s the wrong QR code.
• Looking at the source code of the QR code – it’s encrypted and is not readable there is a private key held on the server.
Back to demo...
• Scan the Vaccinatee QR code and it works and is green “code successfully scanned”
• The simpler the QR code the quicker it scans.
• You can choose to have it in Left / Right Deltoid or Right or Left Quad
• Give the injection, click next… Start here for a new vaccination.
• Let’s show the Vaccinatee Screen Demo –
Q/A:
Mark Palmieri - Has there been any feedback that this process saves time or improves data integrity?
A - Charley: We have had as of ITAC 4049 scans, with 8 problems – 3 related to the recent Facebook data outage – code has been written to go around a data problem. The other was due to a privacy setting on the user's phone.
Shellene – said that if Employee Health has your MRN (Medical Record Number) the updates are pushed automatically.
A- Feedback from Charley & Victor was that nurses love the new scan process because they do not have to key anything in and it moves much faster.
Q: Joanne Van Tuyl – I went to the EOHW place for a shot - it is not used for COVID now
A – Charley – It is used for Flu only not COVID but they do want us to move this over to COVID
The receipt now has the first initial and last name of the Vaccinatee and Vaccinator. It used to be the full name but the change was made for privacy reasons. The name of Vaccinator is required by the state, but limiting to first initial and last name is acceptable.