I’ve kept a work notebook for years. It’s been a place for notes from meetings, ideas for future projects, and to-do reminders. Recently I’ve been looking for ways to make the notebook more efficient and I came across bullet journaling. What immediately appealed to me with a bullet journal is that it is a way to keep the notebook more organized than just a traditional daily journal type set-up and it is extremely flexible to fit your needs.
Now that we have a baby on the way (um, like any day) I want to use the same notebook for my next three months at home. Combining my home and work life into one notebook is also something the bullet journal enables.
Part of the beauty of bullet journaling is that you don’t need much to start. A new notebook is encouraged and who doesn’t love buying new notebooks?! I prefer spiral bound notebooks that I can fold up. I usually buy a few at a time and the ones I have on hand at the moment are Mnemosyne A5 notebooks. I’ve also started using a Pilot Vpen disposable fountain pen. In the last month I bought a pack of Zebra Mildliner highlighters and am incorporating more stickers. For December I bought a pack of Mark & Line Schedule Poyo Animals stickers that work well with a calendar set up.
I’ve been using the bullet journal for about three months now and I’ve realized that the beginning of the month is an important time in the world of bullet journalers. It’s the time to set up your journal for the upcoming month. I wasn’t sure what this meant at first, but now I am keeping lists of what I want to try for the next month.
For December I wanted to have a calendar layout so I could see the whole month at a glance. I used the free font Anders for the inspiration for the headings.
In November I did a daily list that gave each day in the month a line in the notebook, but I realized it just repeated what I put in the calendar layout so I didn’t want to do that again for December. Instead I kept a page for December goals. I also added a page for a monthly budget.
I also added a page outlining a baby (misspelled as baba! F it) feeding schedule, and a circular mood tracker. And I added washi tape to the top of the pages to easily denote a new month. I haven’t done a weekly set up in the past because I like to keep room for daily thoughts and action items. Daily entries range from a third of a page to three full pages of notes, so filling in each day as it happens has been my default mode. I will leave a page or two blank between these month pages and the daily pages just in case there are more baby-centric monthly notes I want to add in.
Below is my presentation for the 10th Annual Conference of African American Librarians which was held in Atlanta this year. I became involved when I saw a call for presenters who had worked with Wikipedia with a focus on diversity. Tiffany Atwater Lee at the Archives Research Center at the Atlanta University Center Robert Woodruff Library put the panel and proposal together and Curtis Small Jr. at the University of Delaware was the third panelist. It was such a pleasure to meet them both and learn about their Wikipedia related projects! All of our slides can be found on Google Drive here.
Intro: I’m Greta Suiter, Collections Archivist at the MIT Institute Archives and Special Collections. I seriously started getting involved with editing Wikipedia after I volunteered to lead an edit-a-thon highlighting collections from the Archives. It ended up being a great way to jump into the world of Wikipedia and has lead to much collaborative work and conference presentations.
Hosting edit-a-thons is a great way for librarians and archivists to share their collections and subject expertise, expand the content on Wikipedia, and teach others about digital literacy, writing, and how to edit. It can be an impactful learning experience that empowers participants to edit one of the most influential websites ever. As we all know if it doesn’t exist on Wikipedia many people are less likely to think it is real or important.
Wikipedia is conscious of its gaps and how it is not actually “the sum of all human knowledge.” Overall it does suffer from systemic bias – the editors, and when you look at the numbers you can see that it isn’t that many editors – around 3500 that are responsible for most of the edits on Wikipedia. And the content that we find represented on Wikipedia will be biased toward their interests. If 80% of editors are white college educated men the content of Wikipedia will reflect their interests. This is one of the big reasons that librarians and archivists should be editing and encouraging others to edit – especially content concerning women and minorities – and especially encouraging women and minorities to start editing.
Wikipedia is aware of this situation and has made some efforts to be a more welcoming and friendly place. The behavioral guideline “Don’t Bit the Newbies” states, “We must treat newcomers with kindness and patience – nothing scares potentially valuable contributers away faster than hostility.” But many new editors still find Wikipedia to be a place difficult to navigate or contribute to.
And it’s been found especially difficult for those working on issues related to underrepresented groups. Encountering accusations of activism, bias, or an agenda can happen and it is especially frustrating when you see the work you are doing as fitting within the Wikipedia mission and ethos, only to be told it is not.
So what are some of the strategies to making meaningful edits that stick in Wikipedia?
One mode of thought is to follow the golden rule – “Articles require significant coverage in reliable sources that are independent of the topic.” In other words you need to prove that a topic is notable enough to be included in Wikipedia. And “notable” can be highly contentious. Arming yourself with sources that support your notability claim is one of your best chances to prove meaningful edits.
This should be easy for librarians and archivists – we are surrounded by reliable sources! And this is where I’ve found most of my work goes into prepping for edit-a-thons. In locating sources that will assist editors in proving notability. Luckily for archivists finding aids do count as a published source.
Here is an example of a stub article that was created using a collection we had titled Black Women in the Academy – it is a small collection that documents a national conference held at MIT in 1994. It was notable because it was cited as the first national conference with Black women in academia as the main theme. The collection consists of newspaper articles, many of which can now be found online, as well as planning documents and program related material. On Wikipedia newspaper articles are considered reliable sources. The collection had enough different sources to start the article and hopefully more will be added to it in the future.
I wanted to share a little about my process of preparing for edit-a-thons. I like to use Google Docs because of their collaborative capabilities. We’ll use a Google doc for brainstorming themes – here’s an example of brainstorming around a Black History Month edit-a-thon. Finding the sources you want to highlight and the entries that need editing or that don’t exist yet in Wikipedia is important to planning the event.
I also find it helpful to keep running lists of edit-a-thon ideas as I come across them – either content that is missing from Wikipedia or resources that would work well to highlight. A recent thrift store find was the African-American National Biography set of reference books. Resources like these are incredibly helpful to editing Wikipedia. Here’s an example of a recent listserv post mentioning the death of a Mexican art historian. I looked her up in Wikipedia and found Spanish and German language entries but nothing in English. This would make a good project because it wouldn’t focus on finding sources as much as being a translation project.
This leads to an important point: There are many ways to edit. You could focus primarily on grammar and language in articles, or on the look of articles – in Wikipedia appearances matter – articles with multiple headings, infoboxes, and properly cited resources are more likely to not be deleted because they look right. Editors can also focus on adding images to the Commons or adding structured data to Wikidata.
Over the course of 8 edit-a-thons that we’ve hosted at MIT over 2 and half years we’ve found when it comes to encouraging new and diverse editors that themes and aligning with larger initiatives is most successful. For us the Art+Feminism edit-a-thons garnered the most interest and we had almost all women editors with many first time editors showing up. This chart shows when we started using the Wikipedia Dashboard for keeping track of edits. So now we can continue to see the impact of the edits over time.
For the last Art+Feminism event we had 18 participants, 1 new article created, 32 articles edited, 199 distinct edits with over 7k words added to Wikipedia, and an impact of 124k article views. This just goes to prove that the goal of editing does not have to be completely tied to creating new articles, but also editing existing ones.
These are images from the Art + Feminism edit-a-thons. We found holding the events in our instruction space which has plenty of computers, and a large conference table worked pretty well. It is not the most beautiful space and there are no collections housed in the space – meaning we need to bring print collections to the space and it is not a typical awe inspiring, Pinterest worthy depiction of a library space, but it is functional much like Wikipedia itself. As we’ve done more edit-a-thons we have increased the number of organizers which has included getting more librarians involved. I would not recommend taking on planning and hosting an edit-a-thon alone. We’ve always had at least two people help with planning and in case of our last edit-a-thon there were 7 of us planning. Through edit-a-thons I’ve been a part of very fruitful collaborations with library and MIT colleagues as well as becoming involved in the New England network of Wikimedians. All of our events have been open to the public. Keeping track of who is attending and following up with them about other events has been the most challenging aspect of organizing for us and something we are hoping to improve in the future.
In the future we are hoping to host an edit-a-thon during Open Access Week that could focus on the importance of Open Access resources.
What I enjoy the most about fiction books (aka novels) is the part in the beginning where the story hasn’t started yet. The reader is unsure at this point of the ultimate trajectory the story will take.
When I attended the CODEX Hack-a-thon at MIT the weekend of February 11/12, one of the first things we did was write out a name tag with our name and the title of a favorite book. My chosen book was the last one I had read — Homegoing by Yaa Gyasi.
Gyasi’s book is an amazing work of fiction spanning centuries and following the progeny of a family divided geographically by the slave trade. Two sisters are at the heart of the novel and each chapter checks in with the next generation — thus positioning the reader always in a state of unknowing what the next story will be — thus avoiding a stale plot.
In the book each chapter is a new occasion for reader and author to explore new possibilities and ideas. The beginning of the CODEX Hack-a-thon had a similar feeling — there was time to meet new people, brainstorm questions and problems, but soon it was clear that one must pick a project, pick a group, and commit to that plot, that story, for the next 24 hours.
Before attending the hack-a-thon I wasn’t quite sure what to expect. I’m not a coder, I wasn’t sure what skills I was bringing to the table. I thought being armed with ideas was my best strategy for being helpful. I brainstormed with colleagues, creating a list of projects that might be worth pursuing. What I learned later was instead of focusing on wish list items (“wouldn’t it be nice if we could do X”) it would have been more useful to come up with specific problems to solve.
At the hack-a-thon there were presentations about sponsors products that we could use and from people that had very definite projects they would work on. After the presentations a number of us still exploring our group and project options joined in a guided design learning exercise. It emphasized the improv ethos of “yes, and”. The exercise let all members of the group express their ideas individually on post it notes. We then grouped like ideas together and then narrowed in on one topic/problem to focus on.
I vacillated between two groups and then chose to work with people interested in the problem of motivation when it comes to long form reading.
From there out it’s not so exciting, this is where the plot drives on. Sure it was fun meeting new people (2 in our group were undergraduate students and alum of AllStarCode (which sounded like a cool program supporting diversity in tech)), but this is the part where all the work happens. And for me, I wasn’t sure what that meant. It ended up being creating a PowerPoint that would explain our project and what the future might hold. Also I got a lot of writing done for another project 🙂 The CODEX atmosphere definitely fosters work and even if I wasn’t working on the hack I had chosen, I still got into and appreciated the focused time.
The app we envisioned, litbit, is a Fitbit app for reading. Something that would magically record and reward the reading one did on a device, or something that you could manually enter data into. The range of data collected and how it was displayed ignited our imagination.
Sunday afternoon was the time to share out what we had been working on. The crowd was very supportive, and most of the ideas were pretty amazing. Some of my favorites:
In the end it was a very fun weekend and it felt like a productive use of time. There was a sense of accomplishment and a sense that I had done something, learned something new, and left knowing how I could have been a little more proactive, with a better appreciation for the skills I already have, and a better idea of what I can bring to the table at future hack-a-thons.
I read exactly 75 books in 2016! It was a personal goal and challenge and the sense of accomplishment is completely gratifying. I’m taking with me my newfound habit of reading daily into 2017 and hopefully well into the future. I’m more excited about my commuting than ever before because now I see it as an opportunity to read more. Most of my reading in 2016 happened during my daily train and bus commute to and from Boston.
I was inspired to keep track of my reading via a spreadsheet by a co-worker’s summary of her reading habits — check out Alli Gofman’s Queery the Catalog. She had a lot of stats for the books she read in 2015 and that inspired me to keep track of what I’m reading in a similar fashion. Here is a link to her post of her 2015 reading in review that includes a link to the Google spreadsheet she uses.
I did some paring down of fields from Alli’s original spreadsheet, but I used most of it. Some of the questions I was very interested to see were how many books were fiction vs. non-fiction, how many books I read electronically vs. a physical copy, male vs. female authors, and how many authors of color was I reading. Fields concerning the main character often became fields about the author when reading non-fiction. Here is a screenshot of my Excel sheet.
E-book vs. book book
63% were e-book.
I love to read books on my iPad mini with Kindle app. I also recently started borrowing e-books from my local public library and I love how easy it is to borrow Kindle books now. It is the most convenient thing to read when commuting, and I like how easy it is to interact with the text. I highlight often and also sometimes write notes. With physical books it is a pain to have to write down quotes in a separate notebook, or to physically damage the book by folding pages (which I do all the time) to mark where I read something interesting.
A breakdown of authors and main characters:
48% were written by women. 24% were written by a person of color. 31% featured a person of color main character. 8% featured a LGBTQ main character.
When it comes to variety of voices represented in the readings there is definitely not as much diversity as I would like to see. I was purposefully trying to read more books by women, and I’m thinking that 2017 will be easier with this. More women seem to be publishing and their books seem to be more promoted and recommended than in the past. I think this is a very positive thing.
When it comes to reading books written by and about people of color I need to make more of an effort to choose those books. The same is even more true when it comes to LGBTQ authors and subjects. I knew that my reading was strongly biased towards hetero-normative white culture but keeping track of the authors and characters really showed me how narrow my reading world is in regards to representation.
Some of my favorite fiction books by authors I hadn’t read before were:
Book 11: Drinking Coffee Elsewhere by ZZ Packer
Book 36: Down and Out in the Magic Kingdom by Cory Doctorow
Book 42: A Thousand Splendid Suns by Khaled Housseini
Book 48: The Paper Menagerie and Other Stories by Ken Liu (this was my favorite fiction read of the year!)
Book 67: Holidays on Ice by David Sedaris
55% of the books were non-fiction.
I love reading non-fiction. I feel like I’m learning something that is real, that is fact based, that I can take and use in the real world. When I read non-fiction I feel like I’m adding to my knowledge of history and how the world works. I know non-fiction can be just as fantastical as fiction, but it seems more worthwhile and less predictable.
When it comes to non-fiction I love to read auto/biographies. I love learning about how people have lived, what they think about their lives and their lineage, and what their experiences were like.
“Academic” I used as a catch all sub-genre to encompass any book that was sort of like something I might have to read for a class. So it actually covers a lot of subjects. It’s not a perfect way of describing these books, but I didn’t want to get bogged down by a ton of sub-categories or subjects.
“Self-help” refers mostly to business-y type books about how to be better at organization or management. These are interesting to read and I also find something useful about them. I consider them mostly quick easy reads that may have some useful advice.
The one that I enjoyed and got the most out of was Book 23: Meaningful: The Story of Ideas That Fly by Bernadette Jiwa. I was interested in this one because it had to do with storytelling as a way to sell products. The main message of the book is that as a business (or an entity with a product/service) you need to stop the cycle of making a product and then finding a customer. Instead you need to know your customers and make products for them, or as Jiwa states, “The blueprint I am sharing with you in this book helps you to start with the customer’s story.” I think we need to do more of that in archives.
Shortest Book: Revolutionary Petunias and Other Poems by Alice Walker — 70 pages
Longest Book: The Name of the Rose by Umberto Eco — 502 pages
Average page length: 141 pages
I wasn’t very surprised that most of the books I read were written in the last few years. There is a lot of hype around new books — reading new books keeps you current, they are the most advertised, and because of that you are excited to read them now. Older books take a little more effort to find out about, they may not be available electronically, and this graph really shows that I’m just less likely to read them. I’m not sure that is something that I want to actively try to change — I like reading new books, but it is something I’ll continue to track.
Oldest Book: Notes of a Native Son by James Baldwin — 1955
Newest Book: The 5th Petal by Brunonia Barry — advanced read, 2017
Reading in 2017
I will be using LibraryThing to keep track of my reading still. But this year I need to focus more on reading for work. I’m hoping to read a lot more articles — I think this takes much more focus and organization, something the past year has prepared me for. I’m also planning to continue reading and keeping track of books, but I am not sure what a more realistic number is — 50 books? 35? This time next year we will see.
This was my second time at the Hampshire College campus this fall. The first was for the New England Archivists fall meeting at the Yiddish Book Center. The NECode4Lib regional meeting was held at a different venue – the red barn on campus. It was a wintry day with snow falling most of the morning, making the drive just as scenic as it was in October when I got to see the fall foliage.
This blog post will give some key points and takeaways from a selection of presentations, as well as some Twitter highlights, and some images from the library tour I took during lunch.
Two themes that struck me as important / reaffirmed my own biases –
1. Users want access to the stuff – not info about the stuff
2. Visuals help engage users – both digitally (click on image / browse by image) and physically (add images / visual interest to library space)
Keynote – Smith (Rob O’Connell and Barbara Polowy) – Bento Box
Will launch new website Jan 2017
EBSCO discover system (EDS) – multi-format materials in one dump – confusing for patrons
Using EBSCO’s framework, not open source
Linking in other content w/ API’s – DPLA
Patrons don’t want to dig down, they just want the resource / content [This was reiterated later in the death to finding aids talk – good to know it exists for libraries as much as for archives.]
StackMap built in – giving location of where item is in the library [yes! It is always confusing trying to find your way around a library!]
There is a feedback button so people can leave feedback [yes! I want to see more ways for people to give feedback!]
Let’s patrons know up front if PDF available
EBSCO research on millennials – use mobile devices (laptops more than phones) for research; skim, scan, seek efficiency; find one good citation and use it to find more.Interactions w/ interfaces: discouraged by large result sets; “chunking” content by format easier to digest; 71% basic searches; Library-ese (jargon) problem; “progressive disclosure” of metadata is helpful in avoiding overloading patrons w/ data
Usability testing – 4 rounds, 20 tests (16 undergrads, 2 faculty); staff sandbox; beta release w/ feedback. Asked them to speak out loud their thought process, answer questions, asked them about citations – how much they need, what they need.
Testing findings – discovery AND ACCESS w/in Bento important; limit citations to essentials; limit to “available at Smith” important
I was impressed by the YBC’s website when I first saw it in October. The fact that they are using a lot of visual images, big font, plenty of white space, and are really pushing their content is inspiring.
Through studies found that users were previously searching for the same thing over and over and not finding it – because Internet Archive API required a 1 to 1 match in searches, diacritic marks also led to non-matches – ended up using Apache Solar for searches
Count Dem Heads: a Fail4Lib story, Ian Walls, UMass Amherst
The best part of this presentation were the hand drawn slides. And that it was told in fantasy story mode. And that it was about a project that didn’t quite work.
He created a digital tool for head counting (not something that comes up much in archives), but it wasn’t very efficient.
Archives are esoteric – not intuitive – we aren’t helping ourselves
FA are the problem – since they are front end to content
FA itself is jargon – broad and general w/ multiple interpretations
FA pre-digital information system
USERS DON”T WANT HELP FINDING THINGS THEY WANT HELP GETTING THINGS
Replace FA w/ web discovery and delivery systems – NYPL system example
FA shouldn’t be end project – we need a new way of talking about it
Make limitations readily apparent – some material is online, some isn’t
Move to on demand digitization
University of Albany new site out in Jan – Drupal – whole site is access to collections – “digital selections”
Serendipity when you refresh the screen new image appears, and 3 random collections at bottom of screen (if they scroll there)
Browse through collections – static html pages – wants to implement ASpace soon
Request stuff on page of collection – even unprocessed collections
“People have hard time discerning part from the whole.”
LUNA for images
Not quite at killing the finding aid yet
Description more important than the finding aid
Folio: Open Source Platform, Andrew Nagy, EBSCO
I’m supposed to know who Marshall Breeding is – he is tracking the less and less choices for libraries
Platform – something people build on top on, an open source development platform
Open source project – collaborative effort
1st library up and running summer 2018 – probably not enough for ARL right away
Habitica, Brendan McCarthy, Troy Public Library
Brendan spoke about using Habitica at work and he has found it to be motivating and engaging. SO I’ve been trying it out at work, but am probably using it wrong. I think you need to check a lot off your list in order to accomplish much, but I’ve got some kind of dragon, and a sword and stuff. The most useful thing about it is that it’s easy to add a to-do and it’s nice to look at when I’m trying to decide what to do next or what needs to be done soon. I guess I’m just using it like a digital to-do list, which is nice.
I liked this idea a lot – a bi-monthly meeting of librarians interested in learning about code.
Topics covered – Python, HTML, XML, xPATH
Met every other week and planned on the off week
Tips: survey participants to see what people want to do; create few simple goals; create/find project that builds up skill level; need 2 or more people planning and working on this; ‘mini-series’ instead of long term club (give people map of what you’ll cover ahead of time, not everyone may need/want to go to every session)
Counted as form of professional development
Future ideas: take apart a computer; WordPress; Github; look at command line interface
I always like the opportunity to find out what my co-workers in different departments in the library are up to. This one was about lighting talks done within a specific department. Seemed like a good way to share ideas, increase confidence in presenting, and build morale.
There was a Twine project at Smith College at last years NECode4Lib and this use of Twine was inspired by that. I have looked at Twine and like the idea of it a lot, but I haven’t actually used it, so hearing about more ideas for use was great.
This presentation was about some interesting cataloging work going on at Yale in reference to African scripts. It was a bit above my head, as archives have much more basic cataloging needs, but understanding Unicode and how it works is something I should have a better handle on, so this reminded me of issues we’ve been having transferring to ASpace and seeing how certain texts are rendering. This also made me think about work we do with materials in languages other than English and how we can improve our documentation around that.
There was a very nice and informative tour of the library during lunch. Here are some pics I took. Highlights included a seed library (!), a game collection, a special collection in the middle of the stacks with lots of custom cabinets, shelves, and seating (that was the best!), a media lab section in the basement, and an art gallery for student work (also the best!).
The New England Archivists fall meeting took place Friday, Oct. 14 in Amherst, MA. It was a great excuse to get out to western Massachusetts and enjoy some leaf peeping. Route 202 was absolutely gorgeous, and there were at least two times that I had to slow down for someone talking photos from their car. Leaf peepers!
The symposium was about as nice as the drive out. It was held at the Yiddish Book Center on Hampshire College campus. I would recommend everyone go out and visit, they have plenty of parking, some very interesting exhibitions, a lovely garden, and many old Yiddish books to buy as well as a gift store.
The theme of the conference was “Bridging the Gaps” and focused on addressing “ways in which we as a profession can reach across the divides between archives and our stakeholders through augmenting outreach and expanding access to our materials.”
NEA Fall 2016 program 1
NEA Fall 2016 program 2
One of the big themes that emerged was the expectations of younger patrons. They are expecting transparency and digital access. Another theme was the importance of human interaction. We heard about this in relation to collecting materials from donors who weren’t sure who would ever want to read an old Yiddish book, to creating outreach events connecting middle-schoolers in Lawrence, MA with local history materials and a Harvard professor, and the importance of going to where your potential users and donors are as in the case of taking archival materials to alumni events at Norwich University.
There were two speakers from the Perkins School for the Blind that focused on access issues when it comes to visual impairments. These had a lot of good practical advice about describing images – describe them – and about how to make a website easier to navigate for a screen reader.
Below are my notes and some pics from the meeting.
Yiddish Book Center – One of the world’s largest and most vibrant Yiddish book centers. Website looks nice, easy to use. Lots of digitized original materials and lots of access to digital files through Internet Archive.
The stacks at the Yiddish Book Center
A bookshelf with duplicate copies
Five ways to read our books sign
Plenary talk by Aaron Lansky
They have about 2% of collection on display – all for sale – all duplicates
Keep electronic masters of scanned books in offices / storage in Bare mountain – which Amherst now owns – used to be gov’t site
Focus now from rescue (was scouring Coney Island – putting up signs saying we’ll take your books) to explaining what these treasures are all about
10k-12k visitors per year – Visitors reaction is often “who knew?” when they see the books
Outwitting History – book Lansky wrote, with news article about the collecting in Coney Island – Doug (fish in Yiddish) McGill
Yiddish movie posters
Famous books translated into Yiddish
Yiddish sheet music
2 quotes at entrance of YBC:
“Yiddish has magic, it will outlast history”
“And who will leaf through these yellow pages?”
4 projects going on:
Universal Yiddish Library (used to be cultural dilution was the way to acceptability, when Lansky growing up they focused on prayer books, not personal experiences – now that’s what younger generation clamor for). Younger Jews want to know all about the culture, it’s ok to be different now. When Lansky started collecting there was shock that anyone would want to save the books, who would read them? “we are trying to forget that past.” Today there are “scores” of young people reading and studying. Most books digitized and online through Internet Archive. They have been online 8 years, and have been downloaded 2 million times. A staggering number. Who is actually reading? Orthodox world is downloading the most, average 9 family size, growing, they all have computers in their homes and they are reading Yiddish books at home. Another large group of readers is younger people studying a range of subjects. Their sources are being read all over the world.
National Library in Jerusalem – they sent hard Drives of Yiddish books, NYPL, wants to create Universal Yiddish Library – all in one place via technology, put everything in same pot – DPLA is example. Partners are thrilled to cooperate. Yiddish not constrained much by copyright. Developing OCR technology which would be revolutionary.
Providing access to more than just books. In Montreal – Yiddish was spoken much more openly, they would record readings of books. The recordings were offered – cassette and reel to reel. 1949 Jewish public library in Montreal free public lectures until 1995 – and they were recorded.
Translating – for a while it was going a book a year. They need to translate from the bottom up instead of top down. They have about 50 people trained – 1 year training program – most of the titles were unknown to scholars.
Education – translation makes it accessible, but also need more communications people helping out and educators. Bilingualism, acculturation, things many immigrant groups deal with – through field trips they get to see what’s going on at Yiddish Book Center. Running programs all over US – 1 week program. YBC still needs funding.
Reason for success – secret weapon is content. To be guardians of culture you have power. There is a lot of power in seeing the books they have for sale / on display, that awes people. Sharing with the world is important and what we should all be doing. Lansky ends with “The calling of activist/archivist has never mattered more.”
Welcome to the Garden sign
More fall foliage from the garden
Yiddish Book Center sign with goat
Panel discussion: Building Bridges: Theory and Practice for Collections and User Access Across Boundaries
Jennifer Arnott – Perkins School for the Blind speaking about accessibility. Users = 49/51 Perkins staff / outside researchers
Things to think about with design of websites
Major thing – allowing people to enlarge the text.
Don’t make people download things
Vocabulary – don’t be so jargon
Multiple spellings – hyphen or no? spellings that change, preferred terms change over time – handicapped / disability; language issues (English as second language)
Screen reader complications, image-based pdfs are almost completely inaccessible, text-based a little better
Don’t autoplay audio/videos
Give people more control over their environment
Tiny links are difficult to see
Congnitive overloads – lots of flashing
Color blindness – purple in use in this presentation
Don’t use “click here”, and url is not helpful either, put the link in the words
Avoid routes – like “red”, “below”, rather say “go to more help section” (and make those words a link!)
PDF accessibility is very complicated because there are multiple layers to the file – STOP IT
Lawrence History Center – German immigrant female founder
Lawrence – immigrant city with lots of segregated neighborhoods. Immigrants have changed – how do the new ones connect to the history of the city? How do you get people to care about the archives – they don’t have time. There is no pride in the city – people want out. Language, cultural, economic barriers – also narrative barrier. Place based learning – use what is around, walking through the spaces of history – you can find history in anything – where you live
They are scanning / taking digital copies of unique materials – and giving originals back to donors
To reach out –
bilingual promotional material
range in speakers – middle schoolers and scholar presented together
Make collections accessible online – partnering with other orgs – BPL and Digital Commonwealth – led to exhibit w/ DPLA, also working with higher ed institutions
Yiddish Print Shop signage
Printers pie, printing block letters
Alana Kumbier – Hampshire College
Queer zines and archival pedagogy
People creating zines – documenting their experience – but not donating to archives
Offer guidance with “Archivist Packet”
Queer zine archive project – establish the relevance of collections – what is context of creation – how are researchers using it
Barnard has big zine collection
beyondtheriot.5colldh.org – Beyond the Riot: Zines in Archives class that brings students to archival spaces – uses local and digital archives – girl zines @ Sophia Smith collection; People of Color Zine Project; Flywheel Zine library @ Flywheel arts space – different archival spaces with different rules – getting students to think critically around that. Not digitizing, but using the zines as primary sources. Students are excited about it. Involving archivists = talking a lot about labor and interventions. Students are concerned about the whiteness of the collections, and the whiteness of the archivists. Asking pronouns on intake forms would be wanted.
Citation – Rawson 2009
Zine core – metadata standard for zines? wanting to record the language that people are using
Music listening section at Yiddish Book Center
Theater at Yiddish Book Center
Shannon O’Neill – Barnard
Accessibility and accountability – analysis of police records of police violence – she looked at police website of 50 police departments – she was looking at what data was available and how transparent were they. Wants more transparency.
Baltimore BPD – leader in accessibility – trying to be more transparent – advertising on front page
How does space effect accessibility – elevators, physical spaces, digital has issues as well
Interpersonal accessibility – with email following their clues – who are they, what assumptions do we make about who is turning up, and do they make about us and the collections
Space online – websites – they are tenuous existence –
Retention schedules – some things just won’t be accessible to us ever
Don’t want to ignore the historical words used, but want to recognize and give info to researchers – that was formally acceptable term, not now
Listen more, communities we serve have a lot of knowledge to bring to us, working with people where they are – not expert telling people what they need to do, but listening and truly figuring out what people need from us.
The Case for Accessible Images – Jen Hale at Perkins School for the Blind. Good description is needed for images. It can be ongoing and organic.
Digital Collections and Emphathetic Outreach: Engaging the Remote User – Molly Brown MLIS student at Simmons. This was a very interesting short presentation about the emotional stakes surrounding archives and how archivists can acknowledge the deep, internal ties to records and then present that info to remote users over the web. How can archivists provide emotional acknowledgement that we are all linked? And how can we represent the emotions of all involved – archivists making appraisal / processing decisions as well as the creators, donors, and researchers.
Uncomfortable Connections: Taking Archives on the Road to Win Friends and Influence Donors – Mary Margaret Groberg at Norwich University. Don’t be afraid to leave the archives and bring collections to potential patrons / donors such as alumni groups.
Introducing the Commonwealth Historical Collaborative – Veronica Martzahl at Massachusetts Archives. This presentation was a quick overview of the Commonwealth Historical Collaborative – a website providing info and small catalogs to mostly local history organizations – such as historical societies around Massachusetts.
I attended the spring New England Archivists conference on Friday 4/1. Here is a summary of thoughts from the keynote address by Caleb Neelon.
I was looking forward to hearing Caleb Neelon speak to a room of archivists. First off because I’m familiar with and excited about his mural work in Fitchburg, MA (my hometown!) and second because I was curious what an outsider to the archives field would bring to an archival conference.
How did a graffiti/street artist become a keynote speaker at an archivists conference? I assume it has to do with the younger generation leading the spring conference programming committee.
How would he relate to archivists? Well, he focused on the sharing of information among graffiti artists in the 1990s. And he talked about gathering primary sources from graffiti artists for the purpose of writing the book The History of American Graffiti. Both of these activities are of interest to archivists because it explains how a group networked and how the primary sources from that group were created, shared, saved, and eventually published.
Like many networks of artists, hobbyists, collectors, musicians, and even professional groups, the graffiti artists Neelon talked about were connected through a shared activity and then a sharing of information about that activity. Neelon explained that every group of young graffiti artist wannabes in the 1990s read the same 3 books – some of the only sources with published images of graffiti – and they all shared information with other graffiti artists in other locales through zines, that got traded and mailed around the world. It was a network of like-minded, creative, and young individuals writing about, and taking pictures of, their work and the work of others that they knew. It was an informal pen pal connection that would perhaps eventually lead to meeting in person and crashing on each others couches. It existed before the internet started changing the speed at which people shared information and it relied on nodes of “graffiti bums and bong shops”. Neelon encouraged any young people in the crowd to forget about a career at the moment and take the opportunity of youth to travel the world couch surfing and networking with like-minded people. I like the sentiment, but feel that for many in the audience they are either past that age, or just find the idea untenable.
Neelon also explained how he came to have a book deal – basically he was in the right line of work at the right time. By the mid 2000s, Banksy and Shepard Fairey were both gaining notice among the general public and the art market, making graffiti an attractive subject for publishing houses. Neelon got a book deal and started gathering source material for a book about the history of American graffiti. Neelon and co-author Roger Gastman were looking explicitly for photos that had never seen a scanner – those that did not yet exist online. This is a challenge when the average age of the graffiti artists were in their teens, and a generation of artists would be about 4 years before a new group of teenagers would take over. The photos they were looking for were taken with cheap cameras and kept not in the best storage conditions. In the end they found related photographs from 250 photographers, and the book is about 400 pages long.
Neelon pointed out that “Not everybody had a real happy ending to their stories,” and that the years of graffiti writing and working with other graffiti writers may have been the high point of their lives. I think this is an interesting point when considering what is saved in archives and how we create context for collections. Archivists document people’s lives by collecting, preserving, and providing access to the material collected. This keynote made me think of the times in people’s lives when they were a part of something bigger than themselves and how that becomes the part of their life that is remembered and saved. It also made me think of social network analysis software and applications in the digital humanities for visualizing social networks.
When questioned if the work of gathering material could have been done by an outsider, Neelon answered, absolutely not. The trust created by the bond of graffiti was what enabled the book to be written and what allowed Neelon access to the source materials. He pointed out that the material may end up in an institution at some point, but for now it still resides with the community.
Archivists are collectors for institutions, and as such, we enjoy learning about new collections – everything from how the items were created, to how they were collected and organized, to how they are shared or used for new research. In that sense Caleb Neelon’s keynote was an interesting look at a specific collection – but the piece that was missing is the long term preservation of the collection.
For me the big take away from Neelon’s keynote is that if archivists want to engage with collectors and creators that distrust, or are unaware of, archives they must find an ally in that group that can then advocate on behalf of the archives. Collecting without building a strong relationship could result in being shut out from a desired collection.
I took part in my fourth MIT Libraries hosted Wikipedia edit-a-thon yesterday! It was a node event for the Art+Feminism themed events happening all over the world. I loved being a part of a larger community of editors; there is something comforting in knowing that you are not alone in your editing pursuits. And of course it is great to be in a room with a group of editors who are willing to help and learn from each other. I always learn something new about editing Wikipedia and about history at these events. At edit-a-thons there is always a tug between getting to know the people there, and focusing on the editing.
During the session I worked on two articles – a draft for Alisa Wells, a photographer who lived and worked in Rochester, New York and experimented with multiple exposures and found glass-plate negatives, and also Ghisha Koenig – a political left-wing artist who created sculptures of people at work in industrial settings.
There were about 20 people who came in during the edit-a-thon, that includes library colleagues, New England Wikimedians, and MIT and other college students. Some stayed for almost the entire time, others dropped in to ask a question and then left. I think art is so important, that is it hard for me to believe there is so much art history missing from Wikipedia. It is great because it is an opportunity to get people that wouldn’t think they would be good editors to start engaging, because if they don’t get it online, no one else will.
A related thing I wanted to briefly write about was an HR training session I went to a little over a week ago on preparing and delivering presentations. It was almost a full day workshop and included a lot of general advice on making presentations. There was also a lot of interactive parts and it was a stressful session for me because of this. We had to actually present twice during the day, the first an extended introduction, the second a presentation we came up with during the workshop. By the end, I had a nice little 3 minute presentation on the intersection of archives and Wikipedia. Here is a draft of that presentation.
With over nine billion page views per month the English Wikipedia is one of the most visited websites in the world. It has over four million articles and over 900 new articles are created every day.
Because it is often one of the first places researchers go for information, archivists and other information professionals should be looking for ways to use Wikipedia both for outreach and community engagement. This article will address ways that archivists can interact with Wikipedia to promote collections, engage researchers, and making meaningful contributions to the largest encyclopedia in the world.
Archivists can promote collections by adding links to archival collections and online resources such as finding aids. Adding links that connect Wikipedia to our collection material will ensure a broader audience knows about our resources. This enriches the content of Wikipedia and is a great form of outreach for the archives.
We can engage users through archives sponsored edit-a-thons. These events bring in a variety of patrons – those who are active Wikipedians and may not know much about the archives, and also those that may know about the archives, but are new to Wikipedia. It is an opportunity to connect with the attendees and learn about their interests, and they in turn can learn about the archives and the important work that archivists do. Unlocking a connection between a person, a collection, and Wikipedia is the ultimate goal. The three work together for a common goal – sharing information about a historic person, place, or event with a broad audience.
One key to making successful edits on Wikipedia is understanding the rules that Wikipedia editors follow and expect others to follow. To create meaningful edits it is important to understand the rules of Wikipedia. This is an active community and we want to adhere to their rules when making edits. Some of the rules to know are what makes a subject notable, no original research, neutral point of view, and conflict of interest.