You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Partnership for Open Publishing
Hi all,
Happy summer! We have some exciting updates below. Please reach out to Caroline or Stacy with any questions or comments.
General Updates
We'revery excited to share that POP is now part of Open Journals Collective (OJC)as a member press.Our membershipmay lead to funding opportunities for participating journals. We’ll share more details as they become available. In the meantime, visit the OJC website for more information.
POP Google Group conversations are now publicly visible so that prospective partners can read about updates and new features. Only invited Google Group members can respond or post.
Meru Updates
It is now possible to embed images in pages via Markdown; the images must be hosted elsewhere and inserted as a link. See the example below:
Meru has launched a new “Preview” feature:
Each collection or item has a "clear cache" action in its header / dropdown menu. For now, if you update a contributor or page that's associated with a collection, clearing the cache manually on the collection should allow you to see the changes that you’ve made without waiting for the default interval-based cache. Sometimes these changes aren’t showing up right away, which is why we now have the preview feature.
You'll now see a sign in button in the Meru header. To access previews, sign in (You'll have to do this even if you're signed into admin in the same browser.), and then select "Preview Mode" from the dropdown:
Once you're in, you should see this banner, which will also allow you to exit back out. You can then navigate to the page that you’d like to see in preview mode:
A note from the Meru developers: “Preview Mode’s primary function is to allow admins and other editors to see entities with visibility set to hidden on the frontend before making the entity publicly viewable. In order tofacilitate this, one of the things we do is bypass the frontend cache when preview mode is enabled. For entities with visibility set to visible, this is the only difference between the preview mode view and the public view. You’re not viewing an unpublished draft. Still, this should allow editors to see many changes without waiting for the cache to expire. This includes changes to an entity’s core properties, as well as changes to entity’s schema properties on its detail page or subpages, such as an article’s metadata tab.Note, however, that bypassing the cache won’t solve the issue we discussed last time where an update to an associated record like a contributor or page doesn’t trigger re-rendering of the entity’s layouts. This is a background job that has to happen in the API for any changes to be visible on the frontend.As we dial things in, Preview Mode might be best thought of as a diagnostic tool: if you’ve made a change in admin and see it in Preview Mode but not in the public view, it’s a caching issue. If you don’t see your change in Preview Mode, we should investigate further. Finally, as a part of this release, we’ve also reduced the cache interval on the frontend.”
Feedback forum: If you would like to meet to discuss the Meru roadmap and provide feedback/input on what features we should develop next, we’d love to set up an informal conversation.