read-status values of “to-read”, “reading”, and “finished”. I’ve managed to tweak my PESOS work flow with Goodreads.com to also include these experimental pieces using the following additional snippets of code appended to the “Body” fields I’ve described before:
&read-status=to-read
&read-status=reading
&read-status=finished
I’ve added one of the three snippets to the appropriate IFTTT.com recipes for Goodreads feeds to create the appropriate output. Here’s the first post I’ve made using the new recipe for bookmarking a book I’d like to read: https://boffosocko.com/2020/02/15/meditations-marcus-aurelius/.
Previously I’ve been using simple notes to create read posts for books and just adding a “read” category to give me more control over the data in the posts. (I only used read posts previously for online articles.) Now that I’ve got the ability to provide some better differentiation for my progress, I think I’ll switch to using read posts for all my reading (books and articles).
Incidentally following IndieBookClub.biz and Indigenous for Android which added support for these earlier today, my method may be the third to use these microformats in the wild. Thanks to gRegor Morrill, Kristof De Jaeger, David Shanske, Ryan Barrett, and Charlotte Allen for their prior work, experimentation, code, and examples for allowing me to get this working on my website.
@c Does your WP site posse to micro.blog? And did you use Granary and micropub for GoodReads?
@c Cool. Read your post and gonna use your notes to set it up on my site.
2020/02/16 18:57
I wonder if it would be possible in the future to add a drop-down box in the Post Kinds editor for Reads, similar to the drop-down for RSVP?
That’s definitely a solid-sounding feature request to post in the issue queue.
It might also make a somewhat reasonable beginner pull request if you wanted to tackle something like in the code.
I’ll note for doing this manually, one could add a database row in mySQL in the
wp_postmetatable with the following values:meta_key:
mf2_read-statusmeta_value:
a:1:{i:0;s:7:"to-read";}Adding this pair will cause Post Kinds to display the Read as the sub-type “Want to Read” in the resulting post. For the other two types you’d want to replace
"to-read"with either"reading"or"finished". I’ve tried it out on a few prior posts and it seems to work pretty well.I might recommend doing this in the admin UI using custom fields, but if I recall correctly, doing it that way will add some additional code that will prevent Post Kinds from finding and displaying it properly.
I guess it might also be something that I could put into a separate plugin? I remember David talking about that a while back for additional kinds. I found the RSVP information in the repository. I might have a look and see what I can do.
Thank you Chris for the encouragement.
As a pre-IndieWebCamp Austin exercise, I’ve gone back and imported all of my Untappd data into my own website. It wasn’t too painful since I only had one post which didn’t include very much data.
To put the cherry on top of the dessert, I’ve created a PESOS workflow that uses my Untappd RSS feed to import future posts into my site automatically using webhooks to my Micropub endpoint. I still need to do a bit of testing and see if I can figure out if there is an mf2 prefix I should be adding to tell Post Kinds that the post is a “drink”. I suspect there isn’t since they don’t really have a microformat associated with them.
Maybe off in the future I’ll tweak the presentation of my drink posts to differentiate between coffee/tea, cocktails, beer, and other generic drinks so that I can have custom per-type icons that match up with the drink types. Maybe I can do it the same sort of way that the Post Kinds plugin has the ability to differentiate Read posts with small differences to indicate “want to read”, “reading”, and “finished”? Though honestly that type of data differentiation may be more trouble than it’s worth, particularly since I’m reading much more often than I drink.
I’ll also want to take a closer look at the IndieWeb wiki for both Untappd and drink/food posts and some other examples before deciding on anything too specific.
Featured image from page 75 of “The human body and health : an elementary text-book of essential anatomy, applied physiology and practical hygiene for schools” (1908) flickr photo by Internet Archive Book Images shared with no copyright restriction (Flickr Commons)
Syndicated copies:
As a pre-IndieWebCamp Austin exercise, I’ve gone back and imported all of my Untappd data into my own website. It wasn’t too painful since I only had one post which didn’t include very much data.
To put the cherry on top of the dessert, I’ve created a PESOS workflow that uses my Untappd RSS feed to import future posts into my site automatically using webhooks to my Micropub endpoint. I still need to do a bit of testing and see if I can figure out if there is an mf2 prefix I should be adding to tell Post Kinds that the post is a “drink”. I suspect there isn’t since they don’t really have a microformat associated with them.
Maybe off in the future I’ll tweak the presentation of my drink posts to differentiate between coffee/tea, cocktails, beer, and other generic drinks so that I can have custom per-type icons that match up with the drink types. Maybe I can do it the same sort of way that the Post Kinds plugin has the ability to differentiate Read posts with small differences to indicate “want to read”, “reading”, and “finished”? Though honestly that type of data differentiation may be more trouble than it’s worth, particularly since I’m reading much more often than I drink.
I’ll also want to take a closer look at the IndieWeb wiki for both Untappd and drink/food posts and some other examples before deciding on anything too specific.
Featured image from page 75 of “The human body and health : an elementary text-book of essential anatomy, applied physiology and practical hygiene for schools” (1908) flickr photo by Internet Archive Book Images shared with no copyright restriction (Flickr Commons)
Syndicated copies: