HMCS Max Bernays Pre-Deployment Brief (May 2024).pptx
Using islandora to build digital collections - 2016.01.29 OLA 2016
1. Using Islandora to Build
Digital Collections
Friday, January 29th 2016 | 9:00 a.m. - 10:15 a.m. | ICTC, Calendon
Kelli Babcock
Dan Lerch
Kim Pham
2. Learning outcomes
1. Understand what Islandora is
2. How the Islandora community and software works to
provide access to and preserve collections
3. Understand why you would use Islandora (use cases)
4. Ingest demo (if there’s time)
3. What is Islandora?
Official Definition
Islandora is an open-source software framework designed to help
institutions and organizations and their audiences collaboratively
manage and discover digital assets using a best-practices
framework.
About Islandora: http://islandora.ca/about
13. Islandora is a community
○ Launched in 2006 at the University of Prince Edward Island
(UPEI). Islandora Foundation (non-profit) created in 2013 to
foster community
• Community delivers two
releases annually, in May &
October
• User driven development
Credit: Erin Tripp / http://islandora.ca/islandora-installations
14. The Islandora Community
○ Large user support community -
https://groups.google.com/forum/#!forum/islandora
○ Frequent training opportunities - Islandora Camps! -
http://islandora.ca/camps
○ Interest groups - http://islandora.ca/if/board
○ Github - http://github.com/islandora
○ JIRA - https://jira.duraspace.org/projects/ISLANDORA
○ Documentation -
https://wiki.duraspace.org/display/ISLANDORA/Islandora
16. Information Technology Services
http://its.library.utoronto.ca
Information Technology Services
http://its.library.utoronto.ca
About us
The University of Toronto:
● 3 campuses (downtown, west, east)
● 84,000+ students
● 6,000+ faculty
● $1.3 billion in research funds (2014)
University of Toronto Libraries:
● 44 libraries
● ~141 librarians
● 1 IT department for the central library system
UTL ITS:
● services downtown campus
● developer, librarian & network services staff
● range of services
● growing demand for digital scholarship support
http://utarmscollections.library.utoronto.ca/islandora/object/heritageutarms2:1912
25. Information Technology Services
http://its.library.utoronto.ca
Information Technology Services
http://its.library.utoronto.ca
What works well for us? What doesn’t?
Great! Not so great.
Don’t need to be a programmer to
use the system
Steep learning curve
Open source (modular and
extendable)
Technical debt with each
customisation
Great access features and
preservation work flows
Scalability of multi-site
environment?
28. Everything our stories has ever done in one slide
● Transferred thousands of records from an ancient database into a
fully formed repository at the archival level
● Edited and corrected thousands of digital objects
● Developed new standards to archive and edit objects
● Utilized the repository as a tool for community engagement
● Indexed the records with Our Digital World to provide a wider
gateway to our repository
29. Lessons Learned, Part I
archivin’ aint easy
Requires in-house technical support
Requires knowledge of archival principles
30. Lessons Learned, Part II
Most things worth doing aren’t easy
Can be a master’s of your own archival fate
Living history
Future citizens will (hopefully) thank us for our work
...Your next major challenge may be around the corner
35. XML tags are just weird looking labels*
Don’t let the next two slides scare you
*Major Oversimplification
36. Marriage Entry in EAC-CPF XML
<cpfRelation cpfRelationType="family">
<relationEntry localType="surname">Corbeil</relationEntry>
<relationEntry localType="forename">Al</relationEntry>
<relationEntry localType="100a">Corbeil, Al</relationEntry>
</cpfRelation>
<cpfRelation cpfRelationType="family">
<relationEntry localType="surname">Thomas</relationEntry>
<relationEntry localType="forename">Marie</relationEntry>
<relationEntry localType="100a">Thomas, Marie</relationEntry>
</cpfRelation>
</relations>
37. Marriage Entry in EAC-CPF XML (continued)
<control>
<recordId>ourstories:30898</recordId>
<otherRecordId>3581</otherRecordId>
<sources>
<source>
<sourceEntry>Innisfil Historical Society</sourceEntry>
</source>
</sources>
<maintenanceHistory>
<maintenanceEvent>
<eventType>created</eventType>
<agentType>human</agentType>
<maintenanceAgent>Susan Stein</maintenanceAgent>
<maintenanceAgency>The Innisfil Scope</maintenanceAgency>
<eventDateTime>1985-08-14</eventDateTime>
<eventDescription>Record stored on microform. Page 2</eventDescription>
</maintenanceEvent>
38. Marriage Entry in EAC-CPF XML (continued)
<places>
<place>
<placeRole>Residence</placeRole>
<placeEntry displayLabel="city">Innisfil</placeEntry>
<placeEntry displayLabel="community">Thorton</placeEntry>
</place>
</places>
<biogHist>
<chronItem localType="marriage">
<event>
Marie is daughter of Mr. and Mrs. Bill Thomas. Wedding took place
at the Trinity United Church, Thornton.
</event>
<date>1985-10-18</date>
41. Dublin Core for a Vital Statistic Object
<dc:title>Marriage of Corbeil, Al and Thomas, Marie</dc:title>
<dc:subject>Marriage</dc:subject>
<dc:description>
Marie is daughter of Mr. and Mrs. Bill Thomas. Wedding took place at the Trinity United Church,
Thornton.
</dc:description>
<dc:contributor>Susan Stein</dc:contributor>
<dc:date>1985-10-18</dc:date>
<dc:identifier>ourstories:30898</dc:identifier>
<dc:source>The Innisfil Scope</dc:source>
<dc:language>ENG</dc:language>
<dc:coverage>North America--Canada--Simcoe--Innisfil--Thorton</dc:coverage>
</oai_dc:dc>
42. Challenges Using EAC-CPF
Limited documentation
Not widely used in comparison to other standards
No official xslt to map EAC-CPF to DC
Not enough simple examples
43. Benefits Using EAC-CPF
Excellent standard to describe people, events, and corporate bodies
Malleable standard that recognizes local conventions
Easy-to-understand tag library: http://eac.staatsbibliothek-
berlin.de/fileadmin/user_upload/schema/cpfTagLibrary.html
Maintenance history: can be used to describe the sources that created the record
Exciting linked data possibilities http://lov.okfn.org/dataset/lov/vocabs/eac-cpf
44. EAC-CPF in Islandora
Created edit form for records using the XML form builder
Used the entity solution pack for metadata display
Added EAC-CPF to SOLR Index (ripped this from discover garden github)
Batch ingested records using CURL script “borrowed” from Donald Moses at UPEI
*Islandora acted weird when ingesting objects without MODs (circa January 2015)
47. Digital Scholarship Unit
2 developers, 3.5 librarians, casual and
student staff
Digital projects, instruction, scholarly
communication, research methodologies
and metadata/data management
48. Move from CONTENTdm
2010 - founding of DSU, limited resources
and infrastructure
2013 - 25 000 in collections of manuscripts,
postcards, images and paintings
49. Move from CONTENTdm
2014 - began migration to Islandora using
metadata mapping and export tools
2016 - beta and production server in operation
61. Different Scholars & Contexts
“Nearby Studies is a joint
program developed between
the Departments of Historical
and Cultural Studies, Women's
and Gender Studies, and
Geography. It aims to focus on
local issues affecting
Scarborough and the eastern
GTA by working with local
community groups, historical
associations, and other nearby
partners.”
Dr. Christine Berkowitz & Partners
61
62. Different Scholars & Contexts
Dr. Jo Sharma & Partners
“The Sherpa project is part of the
Eastern Himalaya Research
Network, which is an
international, multifaceted
initiative around research,
teaching and learning about the
Eastern Himalayas. The Sherpa
project partners with
communities in the Himalayas
for the preservation of Sherpa
culture and heritage through
oral histories.”
62
68. Demo content
While you wait, download the demo content at
http://goo.gl/iQfYMP
After it downloads, unzip the file. Then leave it until the demo.
69. Islandora Documentation Links:
Islandora wiki:
https://wiki.duraspace.org/display/ISLANDORA/Start
Islandora Google Group:
https://groups.google.com/forum/?hl=en#!forum/islandora
U of T Documentation:
● https://connect.library.utoronto.ca/display/CUC/Collections+U+
of+T+Collaborators+Home
Islandora demo
FYI: This is all online!
70. Unzip the file and it should look like this:
FIRST!
Has our demo content downloaded?
72. You need:
1. An image (a file with .tiff extension)
Islandora demo: create digital objects
73. You need:
1. An image (a file with .tiff extension)
2. Metadata (an xml file with .xml extension)
a. This file contains information in it,
marked up with a pre-defined set of tags -
similar to html. This is data about data
and is the data that the repository will
expose for researchers to search upon.
Islandora demo: create digital objects
74. Islandora demo: create digital objects
If you do not have a .tiff file, you can use image manipulation tools such as the
ones listed below to create .tiff files.
Free (Open Source)
● XNConvert - http://www.xnview.com/en/xnconvert/
Not Free (Proprietary)
● Adobe Photoshop - http://www.photoshop.com/products/photoshop
75. If you do not have a .xml file, you can use text editing tools such as the ones
listed below to create .xml files.
Free (Open Source)
● Sublime Text - http://www.sublimetext.com/
Not Free (Proprietary)
● Oxygen - http://www.oxygenxml.com/
Within UofT ITS, we have also created tools to help with this type of work...
● Excel Template -
https://drive.google.com/file/d/0B4VuqV1fiyhcQUdsM3AtWWlMZG8/edit?usp=s
haring
● Excel to XML Converter -
https://drive.google.com/file/d/0B4VuqV1fiyhceENvVU5VWVNQYWs/edit?usp=s
haring
Islandora demo: create digital objects
76. Once you have your .tiff file(s) and .xml file(s)
you are ready to ingest your content into
Islandora!
You can test out Islandora at:
http://islandora.ca/sandbox
Islandora demo: create digital objects
78. You’re logged in as an administrator
Slides by Kirsta Stapelfeldt:
http://www.slideshare.net/digitalscholarship/roots-routes-
introduction-to-islandora
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
81. Click on the Book
Collection
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
82. A thumbnail
image represents
the book cover.
Click it.
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
83. Select the manage
tab
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
84. the book “object,” which is comprised of
“datastreams” - this package of content is
FedoraCommons
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
85. Select the “MODS” hyperlink
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
86. Slides by Kirsta Stapelfeldt:
http://www.slideshare.net/digitalscholarship/roots-routes-
introduction-to-islandora
87. From a book, select “pages”
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
88. click on an image thumbnail
to access a single “page”
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
89. Select “manage”
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
90. Select “datastreams” (the
theme makes it a little hard)
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
91. Multiple datastreams make up
each page
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
92. Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
93. Navigate to basic
image collection
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
94. Select “manage” tab
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
95. Select “Add an object
to this Collection”
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
96. If you had a library
catalogue record, you
could upload it here.
Just select “next”
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
97. Type a title for your
image
Then scroll down &
select “next”
Slides by Kirsta Stapelfeldt:
http://www.slideshare.net/digitalscholarship/roots-routes-
introduction-to-islandora
98. Choose and upload
any jpg file from your
desktop
Then select “Ingest”
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
99. Image appears with a
message that the
object has been
ingested
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
100. Selecting the Manage
tab, and
“datastreams” will
show you all the files
that have been
created.
Slides by Kirsta Stapelfeldt: http://www.slideshare.net/digitalscholarship/roots-routes-introduction-to-islandora
101. Open our demo content and follow along…
1. Batch image ingest:
https://connect.library.utoronto.ca/display/CUC/3.1+Batch+Ingesting+Images+an
d+Objects
2. Book ingest:
https://connect.library.utoronto.ca/pages/viewpage.action?pageId=11405894
3. Creating compound objects:
https://connect.library.utoronto.ca/display/CUC/3.5+Ingest+Compound+Images
Next
Try a batch upload!
Kelli
Dan, Kim, and I will be talking about how our own institutions use Islandora, but before we do that we’re going to cover:
what Islandora is, including the Islandora community and the software stack
then we’ll get into why you might use Islandora in your institution by sharing with you what our libraries have done with it
and then we’ll run through ingesting digital objects into Islandora if there’s time to give you an idea of the platform
Kelli
so what is Islandora?
The official definition of Islandora is that its an open source software framework designed to help institutions, organizations, and their audiences collaboratively manage and discover digital assets using a best-practices framework”. This means it is essentially a repository platform much like T-Space or Hydra. You can use Islandora to create digital collections from a range of file types - from image files, audio, PDF, and even WARCs, and then display this content so that users can search and access it. Or not! You can make collections private as well.
Kelli
the fact that Islandora is open-source means that the software is free for you to download and use
here’s a link to the Islandora Github where you can find all of the code
the code is free but the Islandora software stack is fairly complex, so you’ll need to invest resources in hiring or training staff who have the expertise to actually manage your Islandora repository
Kim is going to discuss the Islandora software stack to give you an idea of the type of software and skills your institution might need to know to run your own Islandora instance
kim
front-end
Drupal is the website that the rest of the world sees. It's really good at letting us build cool things like galleries, maps, exhibits, and timelines.
kim
middleware
Islandora brings Fedora and Drupal together. It adds a ton of important functionality through its solution packs and modules.
kim
back-end
Fedora is where we store all the stuff. It's really good at keeping everything safe and secure.
kim
kim
kim
Every piece of content in Islandora is an object - a collection, an image, the page of a manuscript. Objects can be containers for other objects.
kim
Each object contains several datastreams that describe the object or add elements, like a thumbnail, to create functionality.
kim
Objects relate to each other in a number of ways. An object can be part of a collection (hierarchical) or we can define flat (graphical) relationships.
Dan
Used by institutions around the world, particularly north America and Europe
Check out islandora.ca to learn more
very active on github
https://github.com/Islandora
Google groups
Islandora IRC
Discovery Gardens
Dan remember this!
Kelli
So now that you know a bit about Islandora, we’ll each cover how our institutions are using it.
Kelli
I’ll start by giving you some context for U of T - we’re a big library!
actually, across the university we have 44 libraries, including large campus libraries at our western campus in Mississauga and eastern campus in Scarborough
lots of students, lots of faculty, and also quite a bit of research funding coming in
we have 1 library IT department to support the central library system - which is where I work. It’s called the Information Technology Services department or ITS
we have about 22 staff in total but that includes IT Help Desk Staff, administrative staff, librarians, and network services staff. We currently have 5 developers who all work on a range of projects and platforms, not just Islandora
our department does everything from maintaining the library catalog, library websites, digital signage, to the types of work normally associated with Islandora like digital preservation, curation and digital scholarship
like most other academic libraries, there has been a huge increase recently in the number of support requests from both library departments and faculty who want to build digital collections and digital scholarship projects
Kelli
To meet the growing demand for digital scholarship and digital collection support, ITS created an Islandora multi-site environment that we call “Collections U of T”.
what that means is that we have 1 Fedora repository that preserves all of the content, but multiple Drupal front ends to display and provide access to various collections
We started development in early 2014 and we now have a few pilot projects in the repository as well as 3 sites that have launched in the past 2 years and are actually in production
The original intent behind Collections U of T was to provide a DIY self service for library departments, faculty, and other collaborators across the university to enable more and more people to build and preserve digital collections
We have the parent site - Collections U of T, pictured here, and then a multi-site per department or project
Kelli
Here are some of the multi-site home pages - each multi-site has its own unique URL, and, in some cases unique design, but it’s all accessible through Collections U of T as the portal site. So our intent was to de-silo collections and enable searching across all of these different digital projects to try to enable a) a central place to manage all of them but also b) a central place for users to discover digital content in the library
The repository has been in beta for the past two years to give us time to iterate development, to see what has worked well, and what hasn’t, and I’ll just go through some of the projects that we’ve launched to share with you some of our lessons learned
The Canadian Necrology is the first site we launched on Islandora and it’s actually a good example of making use of Islandora because of its awesome Drupal capabilities
Part of the Canadian Necrology collection is death information for over 4,000 Toronto residents who died from 1853 to 1920.
These records were created by a man named William Henry Pearson (1831-1920). He kept a ledger where he recorded the deaths of friends, acquaintances, and prominent members of Toronto society and made notes about them. The ledger is actually in the collection of the Thomas Fisher Rare Book Library at U of T, and a librarian by the name of Patricia Bellamy administers a database that contains all of the text information from these records
You can search the records by age of the person’s death, their name, what type of job they had - it’s a really great genealogical resource.
The database was migrated from MySql to Drupal content types within an Islandora site.
The Drupal content is indexed and searchable through Solr - top right - while the ledger is browsable through the Islandora Bookreader - bottom right
This project was actually really successful in terms of development and resources. It took two weeks to complete, from start to finish, and involved only 1 information architect who did the design, 2 developers, and then myself in collaboration with Patricia Bellamy. It was a straight database migration into Drupal, and then I supported the ingest of the ledger digital images into Islandora.
So in 2014, after this was done, we thought “ok. Islandora multi-sites. This is a good model for digital projects!” because it was quick (we already had built the Collections U of T repository), we could store and preserve the ledger digital images, which were previously just on a network drive somewhere, and we could also make use of Drupal for the database and searching component.
The second site that we’ve launched is the Project for the Study of Dissidence and Samizdat Electronic Archive.
It was launched in October 2015.
This site is a repository of Soviet dissident periodicals. The digital collection was compiled by Professor Ann Komaromi at U of T. She had a grant project to digitize these materials and make them more widely available through an online repository. She also built resources to complement the digital objects, such as this timeline of rights activism in the Soviet Union - bottom right.
She had funding to digitize the journals, but not much funding for active development on this specific site. So, at first, we attempted this project with no developer support, just librarian support.
This site was a bit of a learning curve.
The first issue that we ran into was the metadata.
You can batch ingest content into Islandora, but after its in there - it is VERY tough to do batch metadata updates. So, for example, we drew up a metadata schema and proposed it to the faculty member; they approved it; but then months later, after content was ingested, changes to the metadata were requested. We didn’t have devoted developer time working on this site, it was only myself, occasional students, and a very dedicated iSchool intern named Rachelann Pisani. So, technically, we could have made metadata updates in a batch method if we had developer support. But because we didn’t have that, there was a lot of manual metadata updates that I would not recommend anyone try to do. So we learned that you need to confirm the metadata content before ingesting.
The second issue was that we ran into was Islandora ingest. If you read some of the community forums, ingest issues happen occaisionally. For reasons that we’re still investigating, some of the image derivative datastreams were not correctly created upon ingesting the periodical pages. This resulted in the periodical pages loading very, very slowly. We eventually had to bring on a developer into the project to investigate and ultimately resolve the performance issue, but it was sort of unexpected technical problem and it delayed the project for a bit
Lastly, this site was the first time I realized that Islandora can’t really be a DIY solution for digital collections. The learning curve is steep. We created extensive documentation for how to ingest content, edit Drupal pages, and edit metadata, but that still required a significant amount of support from ITS to assist the faculty member in working on the project. We still ended up spending significant resources on the site when it was initially intended to be a smaller time investment.
Still, the site launched successfully, the faculty member is happy with it, and it has gotten a lot of good press since its launch last year
Kelli
My last example is a site we actually just launched on Monday - the French Renaissance Paleography project, a website that provides scholars and students the opportunity to practice paleography.
Kelli
Paleography, if you’re wondering, is the study of handwriting. The website provides a set of pedagogical paleography tools as well as 100 manuscripts from the French Renaissance period.
Kelli
Supported by a grant from the Mellon Foundation, the three year collaborative project was led by the Newberry Library, in partnership with Saint Louis University, the Iter project, and the University of Toronto Libraries. The Paleography site is hosted by us in ITS
We built the site using the Islandora[2] because we wanted a preservation platform but also knew we were going to need to build customised tools, such as the Islandora Mirador Bookreader viewer[3] and T-PEN Connector module.
I won’t go into T-PEN, but one of the major tools on the site is a transcription tool that is a customized version of the T-PEN software, developed by the Center for Digital Humanities at Saint Louis University - so we built the T-PEN Connector module to integrate this tool into Islandora
Kelli
This was not a small project! We have been working on it for two years, had a full team of developers and network services staff, and invested a lot of resources in the creation of the site.
One of the neat tools that we were able to build because Islandora is open source is the Islandora Mirador Bookreader viewer.
Mirador is actually an existing image viewer developed by Stanford and based on the IIIF (International Image Interoperability Framework) standard.
It was a goal of this project to have the manuscripts be IIIF compliant and also the project partners really liked the Mirador viewer over Islandora’s Internet Archive Book viewer, which you’ve seen on past slides.
So our team took the Mirador code and plugged it into Islandora - which sounds simple, but actually took a lot of development time, and now we have this great alternate viewer in Islandora for manuscripts.
Mirador allows you to do neat things like invert the colours to better read the handwriting, you can compare pages, and the IIIF standard enables us to share these images with other IIIF compliant repositories.
We’ve had a lot of positive feedback about the site and most of the comments so far have been around this viewer and how useful it is for exploring the manuscripts
Of course now the question is: how do we allocate resources intelligently in our over-scheduled department to ensure we’re able to contribute this code back to the Islandora community so it can be something that is sustainable and re-used? The grant period is over, we’re moving on to other projects, and don’t necessarily have the time to submit this code and maintain it with the Islandora community. We do plan to submit it to Islandora Labs, but for now it is just on our local UTL github
Kelli
To recap, there are some great things about Islandora but in our particular institutional case, there are some not so great things
So first, it’s great that you don’t need to be a programmer to use Islandora / but you probably need some time to climb the steep learning curve hill of how Islandora works and then still also need network services and developer staff to maintain the platform for you
It’s great that it’s open source and modular, we’ve been able to meet a lot of project needs with the platform. But customisations, no matter what the platform, lead to technical debt so we have to evaluate our customisations against the resources we have to maintain them for the long term
Lastly, it’s great that Islandora out of the box has good preservation and access work flows, but we’ve begun to question the scalability of our multi-site environment
One thing I didn’t mention about the Paleography site is that we actually had a number of performance issues with the site, so much so that we rebuilt an entirely new Islandora server architecture dedicated just to Paleography so that we wouldn’t have performance issues. Now we have to go back and look at our multi-site environment and assess if it is really a solution for any new incoming digital projects.
Our islandora repository is known as our stories, which you can find at www.ourstoriesinnisfil.ca
IPL is the facilitator between members of the public, local groups, the Innisfil Historical Society (ect)
Our stories has been around for about 4 years now
IPL is the facilitator between these groups and curate and house the digital collection
ex) culture days, stroud 100th anniversary, community stories such as WW1, agriculture ect
This is particularly true if you are using islandora as opposed to going straight to a vendor
Regardless of a platform that you pick, staff are going to need to learn about basic archival standards
don’t have to worry about a 3rd party’s echo system
Think of the humans of new york project
Islandora objects, suchs and MODs and DC are represented in XML
We had to research another archival standard that most closely matched the records we had; MODs is not suitable, but need something “richer” than just Dublin Core
Before we talked about the essential objects in Islandora, such as MODS, DC, RDF, FOXML. They are represented in XML
BTW - we change our labels for main displays
Keywords
For searching the repository, consistent Dublin Core design is essential
Dublin core required in islandora. Doesn’t give you as many fields (labels) to work with, but highly malleable
mention renewed appreciation for the dublin core standard as pretty much anything can be described with it
the issue with maiden names was easily resolved, but the fact that every example for a person was male may speak to a larger issue above my paygrade
Describe what each of these means for the uninitiated
Remind audience to email me if there are questions
focus on special collections and projects
Kim
2 scholars coming to us
chris berkowitz coming into the DSU
Kim
Jo scholar we’ve been working with on other projects
Lingling
With the funding from Dr. Chris berkowitz we were able to support Pinedrop to abstract and develop Transcript UI module.
Dr. Jo Sharma is submitting a grant application (SSHRC) that will also include money for continuous development work. Therefore this project emerged as the result of a unique joint partnership between the Digital Scholarship Unit at the University of Toronto Scarborough library, two scholars in UTSC’s History department, and Pinedrop, a Drupal services company specializing in digital scholarship applications, and demonstrated how we utilized an open-source approach for sustainable and agile application development.
other interest - florida FVC, UVA, Minnesota State Colleges and Universities
many prior examples of interest in archiving oral histories
Chris Berkowitz - annotation
Jo Sharma - translation of transcripts
Other faculty member
Pinedrop - Web solutions for scholarly institutions and communities
quite similar requirements
Both have videos that are multilingual, both have videos trying to capture a population disappearing and under heard
record what saying but enabling scholars to make some description of what they’re saying later on analyze
immigrant histories in scarborough now
Chris - different languages
multicultural historical association, archives and teaching
later wants students go out and do oral histories then will later do annotation
development of sherpa cultures in the himalayas - labour history
Nepal - some Hindi, etc
Himalayan club, public schools in India
wants to bring in students
preservation and access of oral histories
sites/presentations we use content from here
using examples from these slides https://docs.google.com/presentation/d/1eLIDDyxC-M1e8eQCrkMK3c2xtumonJRn3lU-zDcVlnw/edit#slide=id.gbf1837dbc_0_4
http://sallain.github.io/islandora-intro-clga/#/
kelli
Kelli
in addition to the Islandora Documentation links above, our UofT ITS department has developed documentation so that content collaborators can learn how to batch edit image and metadata files before ingesting them to build digital collections
documentation enables content collaborators to take the lead in building digital collections
also offer support - can email us with questions and also attend sessions like these
Kelli
- create the digital objects (images & metadata)
- need two files:
Kelli
- create the digital objects (images & metadata)
- need two files: .tiff file
Kelli
- create the digital objects (images & metadata)
- need two files: .tiff file
and .xml file
Kelli
Kelli
Kelli
Kelli
We’re logged into Drupal
Let’s look a little deeper at one of our objects.
Click Manage on our book and Look at Datastreams.
Biggest integration is with FedoraCommons.
Back to the datastreams and look at XML datastreams
- What is XML? why store things in XML?
- metadata encoded in XML (MODS format - one of many metadata standards that make your data interoperable, and ensure its legibility to other systems)
Return to discussion of formats.
This is where the actual content of the book resides, in its individual pages. There is a jp2 file, a PDF, a JPEG, and OCR/ HOCR datastreams. These were created automatically (which is why we have two jp2 streams). Typically the original object would be a .tiff file.
An Archival Information Package
Additional datastreams could be added to, for example, contain TEI text or a security policy.
