Closed rduerr closed 7 years ago
Karen, here are my comments on the draft video:
Here is an updated version: https://www.youtube.com/watch?v=dOGpHpP_WcA
Things that I suspect need more work...
1) The wording on the "how it works" bit, which you mentioned above (#9). Still needs to be clearer and needs to represent that intercepting services don't necessarily modify the request and that there may be more than one.
2) I added the other features of core Fedora API, maybe it's too much now I can cut it any way you like!
3) Input on coverage / accuracy would be helpful - I think maybe I need to mention Linked Data Platform somewhere at the start.
4) Perhaps there is a better way to go through the examples - drawing a blank on how to animate that.
5) Some of the transitions are rough - I will fix them when we're done rearranging things as they break when I move things.
6) Need some info to put at the end e.g. a contact, a website, instructions how to learn more.
This is great @karenhanson. Two initial comments:
Even if we end up cutting some of the core Fedora services from this video, I would like to keep the segments for other videos. You have done a great job of depicting them in intelligible ways.
@fcrepo4-labs/fcrepo-api-x-dev, Could all who are interested in reviewing and commenting on the video do so before next Monday? @karenhanson posted an updated version last week. She'll start working on the final version next week. https://www.youtube.com/watch?v=dOGpHpP_WcA
@karenhanson - This is great already! I’d like to show it to my ELOKA team even in its current state. Would you mind if I did that? By the way the examples of what can be done with API-X are perfect - now we just need to get folks to implement them….
On Nov 28, 2016, at 11:13 AM, Hanh Vu notifications@github.com wrote:
@fcrepo4-labs/fcrepo-api-x-dev, Could all who are interested in reviewing and commenting on the video do so before next Monday? @karenhanson https://github.com/karenhanson posted an updated version last week. She'll start working on the final version next week. https://www.youtube.com/watch?v=dOGpHpP_WcA https://www.youtube.com/watch?v=dOGpHpP_WcA — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/fcrepo4-labs/fcrepo-api-x/issues/88#issuecomment-263348008, or mute the thread https://github.com/notifications/unsubscribe-auth/ABeSvDTE9GYKYaQThGVDbYpjhY459kMjks5rCxmsgaJpZM4KvaZh.
@rduerr yes, please feel free to show the rough version - I welcome any feedback from the ELOKA team as well! The link will change when we load the final polished version, so we should wait to share the link more broadly. At minimum I will need to correct the two things mentioned by @awoods, add some contact info at the end, and polish up the transitions.
Thanks for putting this together. It looks great! I noticed a typo at 2:35 (should be geospatial), and I also think it might be better to say, rather than "expose IIIF-compatible views of images", something like "enable IIIF services for image data". This seems more accurate for how API-X will likely be used, namely as the glue connecting Fedora to a IIIF compliant image server. Apologies if this seems like hair-splitting...
Here is an updated version that includes everyone's feedback. Please let me know if I need to change anything else before I polish the timing and transitions and publish the final version. Thanks! https://www.youtube.com/watch?v=gACfN4wXGOw
@karenhanson: I think it looks great. I particularly like the section detailing the various domains and how they might use API-X -- that seems like it will be very effective in communicating the importance of this work to the wider world.
Here is the final public link: https://www.youtube.com/watch?v=4BgnbMlzYUM MP4 available here: https://drive.google.com/open?id=0B9klf6ZJ3Q3lXzc2aHJNUEd6clU Thank you all for your input!
This should be based on the documentation provided; but scripted to demonstrate to repository managers and other management types why API-X is something they should care about and support (i.e., to describe what it can buy them).