262
edits
Changes
Add the process
So we want to reorganise to collection into some kind of storage solution that enables people to open a box knowing that something they're looking for will be inside. We think that before designing and building this solution, we need to know what's in the boxes. We'd like to design a system that responds to the context the collection finds itself in. Our first step to inviting people to contribute to this design is to discover what is in the collection by cataloguing it.
== The process ==
We use a Google Form ([http://goo.gl/drZn35 http://goo.gl/drZn35]) to capture the information we want to note down about each ephemera work to be catalogued. For each work we collect:
* the number of the box it came out of (1-6);
* its title;
* the URL for it in the Australian National Library’s Trove database (we can use this link to pull all kinds of useful information from their records later);
* a photo of its cover; and,
* if it isn’t represented in Trove: the author, publisher, year published, and language.
The basic cataloguing process is:
1. Grab:
* a bunch of items out of the box that we're currently working through (box 2 as of 2018-03-12).
* the transparent plastic 'done' box for items that have been catalogued in the current box.
2. Pick up an item to catalogue.
3. On your phone, go to [http://goo.gl/drZn35 the cataloguing form at http://goo.gl/drZn35].
4. Answer the questions on the form for the item, including taking a photo of it's cover.
5. Once your answer is submitted, put the item in the 'done' box.
6. Repeat :)
The responses go to a spreadsheet you can work with, and you can also access a data feed of the entries via a public URL, if you open up the share settings (see my example of requesting and parsing that data feed).
This spreadsheet will form the initial version of the catalogue. We'll then pull more information out of the Trove collection where possible and make a master sheet that we can then share and analyse as we design a system to organise the items.
At the book fair was an issue with the uploading stage of the Google Form regularly crashing the browser of the device the cataloguer was using. This was very frustrating as the cover photo capturing was at the end of the form and it would cause the person to loose their work for this item. As the form was quite short, this frustration wasn’t a blocker to people continuing to catalogue works. There may be a need to try a system that is less memory intensive on the devices in the future.
All the cover photos are taking up a lot of space in Google Drive. We've received a notice that we're close to our space allowance.
== Backups ==
We need to set up some backup system of our catalogue and the item cover photos. Sending them over to the [[Internet Archive]] using something like [[morph.io]] could be a good solution.
== Links ==
* [http://goo.gl/drZn35 The cataloguing form]
* [https://docs.google.com/spreadsheets/d/1ipWHrciUS_b1kYWEJokNGVrDaTJsYS1LfpWY-nX0jag/edit?usp=sharing Spreadsheet with the working catalogue]
* [http://equivalentideas.com/journal/frontyard-at-volume-2017/ Luke Bacon’s write up of the Volume Book Fair catalguing event]
