Skip to content

Latest commit

 

History

History
117 lines (70 loc) · 9.05 KB

index.md

File metadata and controls

117 lines (70 loc) · 9.05 KB
Raw
layout title manifests loaded_manifest
page
1. Select a Manifest
heresies_01
heresies_02
heresies_03
heresies_04
heresies_05
heresies_06
heresies_07
heresies_08
heresies_09
heresies_10
heresies_11
heresies_12
heresies_13
heresies_14
heresies_15
heresies_16
heresies_17
heresies_18
heresies_19
heresies_20
heresies_21
heresies_22
heresies_23
heresies_24
heresies_25
heresies_26
heresies_27
sinister_wisdom_8
sinister_wisdom_9
sinister_wisdom_10
sinister_wisdom_11
heresies_01
<script src="https://use.fontawesome.com/884e80fbb8.js"></script>

Sample pre-loaded annotations can be viewed by toggling the button on the top left of the viewer.

{% include iiif_presentation.html %}

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.


{% include annotation_to_json.html %}

3. Store Annotations


<iframe width="100%" height="500" src="https://www.youtube-nocookie.com/embed/nHbsm8T1BnI?rel=0&showinfo=0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>

4. Annotation Instructions

  1. Navigate in your terminal to the folder where you have saved the annotate folder within the AdArchive 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).

  2. Checkout the master branch with the command: git checkout master. If this is the first time you are using this branch, you may need to run git fetch first.

  3. 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)

  4. In the terminal window, serve (ie: run) the Jekyll software by typing in: bundle exec jekyll serve.

  5. 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.

  6. 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.

  7. 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.

  8. Click on the speech balloons icon in the top left corner of the viewer window to open the annotation tools.

  9. Select the rectangle annotation lasso.

  10. Draw rectangle lasso around first annotation and release. When you release the lasso, a text box will pop up.

  11. 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.

  12. In the tag field, tag the item as an advertisement by typing “advertisement” into the text field.

  13. Once you are done capturing the information required, hit Save to close window (or hit enter on your keyboard)

  14. 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 enter "advertisement_image".

  15. Repeat for all remaining advertisements for the issue. Do not include subscription forms, as these are not advertisements.

  16. 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.

  17. At the bottom of this box, click on the “Download [page number] JSON” button.

  18. 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.

  19. Copy the annotations file (its name will be [page number].json) and navigate to the annotate folder you have saved on your computer.

  20. Open the ‘annotations’ folder within the ‘annotate’ folder.

  21. Select the issue you’d like to save to.

  22. Paste in the folder for the proper issue number.

  23. Repeat for subsequent pages.

  24. 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>inspect>application>storage>and then click on “clear site data”.

  25. Next, return to the command window to stop the Jekyll serve command by typing: “CTRL-C”.

  26. 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 command git reset --hard. This will reset all of your changes to the latest commit.)

  27. To commit your changes, type: git add --all and then git commit -m "annotations for [issue_number]"

  28. To upload your changes, first merge your working branch with the master branch by checking out the master branch with git checkout master. Then run the command git merge [name of working branch]. If an error occurs in the merge process, abort the merge with git merge --abort, upload your working branch by checking it out and using the command git push -u origin [branch_name], and contact the repository administrator to complete the merge process.

  29. If the merge is successful, push your changes to the master branch by typing: git push origin master.

5. Adding manifests to annotate new issues

  1. Upload the issue to Internet Archive
  2. Navigate to the annotate repository in your terminal
  3. Create a new working branch of the master or gh-pages branch for your changes. Use the master branch if you wish to annotate the issues by running jekyll locally and the gh-pages branch if you wish to annotate them online
  4. 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.
  5. 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 selecting File>Save Page As in your web browser. Save the file as manifest.json, ensuring that there are no trailing numbers in the name, such as manifest (1).json.
  6. Create a folder in annotate/iiif/ with the name of the issue. Use the format [publication]_[number] e.g. sinister_wisdom_11
  7. Copy manifest.json to the new folder.
  8. In your terminal, from the annotate folder, run bundle exec rake
  9. 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.
  10. To commit your changes, type: git add --all and then git commit -m "added manifest for [name of issue]"
  11. Merge your changes to the appropriate branch, and push them.