Comments (14)
@jaimemears This relates to #51 somewhat... I was just reading through the IIIF meeting notes from Glen, Josh and Meg, and was wondering about a comment you made regarding other Library systems or organizations using this app.
One way would be to host this app's code on their own website/server of course, and they could feed the application whatever images they wanted.
Another way others could use the app, would be if the SA app was hosted by LOC, and outsiders fed in their own IIIF manifests (through a form input pointing to a IIIF manifest URL, or file upload), which imported a user IIIF manifest which contains references to their IIIF hosted images. And the application would dynamically update it's source images, instead of hard-coding them like we're doing now.
Just curious on if this is what you may have been thinking?
from loc-speculative-annotations.
from loc-speculative-annotations.
@jaimemears For option 2, nothing that technical. I was referring to "hosting" as just whatever hosting environment this application lands. What I was referring to is the act of selecting images being part of the application itself. A lot of IIIF UI interfaces are designed to be agnostic to source materials, and then you feed generic apps IIIF manifests and they display the content.
Not suggesting we go this route, but thought one of your comments in the email thread from Josh/Glen/Meg was asking about extending the app's functionality to other institution's materials.
We can chat more about it if it's still unclear.
from loc-speculative-annotations.
As of this PR (8f3da7a) Work's metadata is now being delivered by IIIF manifests.
Since this is a single page application, we can't really serve the manifests so for now we'll store the IIIF JSON manifests in /public/iiif
in order to mimic Promise-based retrieval.
The top-level application IIIF manifest is public/iiif/speculative-annotations-manifest.json
, which a type: Collection
manifest storing information about all containing works and the application itself.
In the top-level manifest, the items
property holds the individual manifests for each Work, which holds all the metadata for each work.
In the public/iiif/
folder, there are numerous folders which each represent either a local application Work, or a very simple IIIF manifest file which represents the parent LOC collection (or search if a collection is not referenced by @jaimemears ) that contains the Work.
/iiif
/duchess
/federal-threatre-project
info.json
/national-park
/wpa-posters
info.json
...
from loc-speculative-annotations.
@jaimemears I'm putting this into the "Needs feedback/action" Project column in the Github project, in case you'd like to schedule a bit of time to go over the general structure of how these Manifests are organized, and how we'd go about updating them on either of our ends?
from loc-speculative-annotations.
from loc-speculative-annotations.
@jaimemears I could do tonight if you'd like? I'm free anytime after 6pm. Zoom or something with screen share will probably be helpful? If you want me to set something up, lemme know?
from loc-speculative-annotations.
from loc-speculative-annotations.
Sure thing, that works.
from loc-speculative-annotations.
From @jaimemears
https://www.loc.gov/item/mal0063800/manifest.json
...our developer said that there should be manifests for most thinks if you use that file structure. if you get a 500 or error, lmk and i can slack them to fix the issue.
from loc-speculative-annotations.
LOC IIIF manifest locations:
National Park manifest:
https://www.loc.gov/item/2007676133/manifest.json
Walt Whitman:
https://www.loc.gov/item/mss1863001302/manifest.json
Duchess
https://www.loc.gov/item/ihas.200218724/manifest.json
Filmstrip
https://www.loc.gov/item/2007660344/manifest.json
Ice cream soda
https://www.loc.gov/item/2017819414/manifest.json
from loc-speculative-annotations.
Cool so the manifests are there so far! How’s the parsing looking btw 2.0 ->3.0?
from loc-speculative-annotations.
@jaimemears Yes, pulled the LOC manifests into the SA application and am pushing updated code now. The application now is using a hybrid of LOC hosted manifests for data, and our local 3.0 manifests.
So basically the parent Collection manifest (our own) contains an items
array of Works. The Works are wrapped, more or less by our own local manifest authoring, but reference the LOC manifests for any data we can pull from the LOC source. If the data the app uses is not available in the LOC manifest, we're storing and retrieving that info locally.
Any questions, let me know and we can also walk through the updated structure if you like.
You can view the updated code in these commits:
from loc-speculative-annotations.
makes total sense. Thank you!
from loc-speculative-annotations.
Related Issues (20)
- "Placeholder for generic collection" language in metadata panle HOT 3
- update Hurston Curator Annotation HOT 1
- remove red from color palette
- update Brown v Board Curator Annotation HOT 1
- Mink letter UID update: Item 2011660380 to be replaced with mm2003084957 HOT 1
- Update About to include open source description HOT 2
- Metadata updates to Mink and Milhous HOT 4
- update 2 curator annotations HOT 1
- remove red curator color from color palette
- update Brown v Board curator annotation HOT 13
- updated about page with PR
- Update ask a librarian link for sn83045462-19571104 HOT 2
- replace default homepage item HOT 1
- replace Pecan Sheller curator annotation HOT 1
- move 48038600 to the opening page (making it item 1) HOT 1
- update Brown v Board annotation HOT 1
- add Lincoln curator annotation mal.0773800 HOT 1
- Remove item 2018677694 from application HOT 1
- Remove item numbers from teach page HOT 1
- Inconsistent package metadata
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from loc-speculative-annotations.