1. Select a Manifest
Sample pre-loaded annotations can be viewed by toggling the button on the top left of the viewer.
Switch between objects by clicking in the top left corner, followed by Replace Object .
2. Add Annotations
Make sure you are on Image View then toggle the Annotation panel.
Add one or more annotations to one or more pages. Then click the ‘view cached annotation JSON’ button below.
*Note: This will only include new annotations added in the browser.
3. Store Annotations
4. Full Annotation Instructions
-
Navigate in your terminal to the folder where you have saved the
annotate
folder within theAdArchive
repository. For example, if you have saved the repository on your desktop, you would type:cd Desktop/AdArchive/annotate
. (The annotate folder is its own repository within the AdArchive repository, so changes are treated separately). -
Checkout the
gh-pages
branch with the command:git checkout gh-pages
. If this is the first time you are using this branch, you may need to rungit fetch
first. -
Create a new branch with the name of the issue you are annotating. For example, if you are annotating Sinister Wisdom issue 1, you would type:
git checkout -b sinister_wisdom_1
(this command is a shortcut to both create a new branch and check it out) -
Begin annotating. Under the
#1 Select a Manifest
heading (above), click on the issue that you will be annotating. Be sure to check which annotations have already been done so you are not duplicating your own or someone else’s work. -
Once you have clicked on the issue that you will be annotating, a new viewer window will appear with multiple page images from that issue. Scroll to the bottom to find the first page of advertisement images, which is usually on the last 3 pages of the magazine issue. Click the first page of advertisement images.
-
Hit the full screen icon in the top right corner of the viewer to make the screen large enough to see the full page of advertisement images so it is big enough to select the annotations. To zoom in and out, place two fingers on your track pad and move fingers up and down.
-
Click on the speech balloons icon in the top left corner of the viewer window to open the annotation tools.
-
Select the rectangle annotation lasso.
-
Draw rectangle lasso around first annotation and release. When you release the lasso, a text box will pop up.
-
In the text box’s text field, enter who the advertisement is for (e.g.: “Soho 20”). If the advertisement title is different than the item that is being advertised, add the title of the advertisement in a line that follows (e.g.: “Title: Read Soho 20”). Normally the advertisement title and the item advertised are the same thing.
-
In the tag field, tag the item as an advertisement by typing “advertisement” into the text field.
-
Once you are done capturing the information required, hit Save to close window (or hit enter on your keyboard)
-
Follow the same process for all images that are a part of the advertisement. This includes logos and other illustrations. In the text box enter
[Name of advertisement] advertisement image
and in the tag field enteradvertisement_image
. -
Repeat for all remaining advertisements for the issue. Do not include subscription forms, as these are not advertisements.
-
To save annotations, scroll down in the browser window past the viewer window to “#2 Save Annotations”. Click on “view cached annotation JSON’ button. A box will appear with JSON in it, organized in sequential order by page number.
-
At the bottom of this box, click on the
Download [page number] JSON
button. -
The annotations will be saved to your downloads folder. Ensure that the file names are formatted with just the page number, followed by the “.json” extension, e.g.
0.json
and not e.g.0 (1).json
. If not, rename them. -
Copy the annotations file (its name will be
[page number].json
) and navigate to the annotate folder you have saved on your computer. -
Open the ‘annotations’ folder within the ‘annotate’ folder.
-
Select the issue you’d like to save to.
-
Paste in the folder for the proper issue number.
-
Repeat for subsequent pages.
-
Next, you will need to clear the cached annotations from your browser storage. Scroll down to “#3 Store Annotations” step 6. In Chrome, right click on the page, select
inspect>application>storage
and then click onclear site data
. -
Next, return to the command window to stop the Jekyll serve command by typing: “CTRL-C”.
-
In the command line, store your annotations in subfolders and create a copy of the IIIF manifest by typing:
bundle exec rake
. (Note: If you encounter a problem in the process, or make a mistake, you can restart from scratch with the commandgit reset --hard
. This will reset all of your changes to the latest commit.) -
To commit your changes, type:
git add --all
and thengit commit -m "annotations for sinister_wisdom_1"
-
To publish your changes to the website, merge your working branch with the
gh-pages
branch by checking out thegh-pages
branch withgit checkout gh-pages
. If an error occurs in the merge process, abort the merge withgit merge --abort
, upload your working branch by checking it out and using the commandgit push -u origin [branch_name]
, and contact the repository administrator to complete the merge process. -
If the merge is successful, push your changes to the
gh-pages
branch by typing:git push origin gh-pages
. The website should update with your annotations within a few minutes. If you encounter any problems, please contact the repository administrator.
5. How to Add New Manifests (To Annotate New Issues)
- Upload the issue to Internet Archive
- Navigate to the
annotate
repository in your terminal - Create a new working branch of the
master
orgh-pages
branch for your changes. Use themaster
branch if you wish to annotate the issues by running jekyll locally and thegh-pages
branch if you wish to annotate them online - Go to the archive.org page for the issue you wish to add. The last part of the URL for the issue page functions as the id to identify the issue on Internet Archive. It should appear in the format:
https://archive.org/details/[id]
. Note the id for the issue. - Download the manifest from archive.org. The manifest will be located at
https://iiif.archivelab.org/iiif/[id]/manifest.json
, replacing[id]
with the id for the new issue. For instance, the manifest for Sinister Wisdom 11 is located at https://iiif.archivelab.org/iiif/sinister-wisdom-11-ads/manifest.json (Note: the manifest will take a few minutes to generate after you upload the issue to archive.org). Navigate to the file in your web browser and save it to your computer by selectingFile>Save Page As
in your web browser. Save the file asmanifest.json
, ensuring that there are no trailing numbers in the name, such asmanifest (1).json
. - Create a folder in
annotate/iiif/
with the name of the issue. Use the format [publication]_[number] e.g. sinister_wisdom_11 - Copy manifest.json to the new folder.
- In your terminal, from the
annotate
folder, runbundle exec rake
- You may wish to run Jekyll locally to ensure that the new issue was added successfully. Do so with ‘bundle exec jekyll serve’ and navigate to
http://localhost:4000/annotate/
. The new issue should appear in the gallery. - To commit your changes, type:
git add --all
and thengit commit -m "added manifest for [name of issue]"
- Merge your changes to the appropriate branch, and push them.