Skip to main content

Feature Frenzy #1: The Cure for Post-Publication Panic

Tizra isn't the same software it was a year ago. Or even a month ago. In this series, we'll outline a few recent upgrades that are making our software more useful and valuable all the time. Upcoming posts:
Today: Quick fixes and updates with new publishing options.
Ever have post-publication panic…that sudden chill when you catch an error right after clicking "Publish to Live"? Fixing these slips has always been pretty easy with Tizra, but now it's quicker and your users need never know it happened…even if you goofed on a LARGE scale.

Say, for example, you misspelled the name of your Very Important Author on her latest, thought-leading report. As always, you can just type in your changes and click "Publish," but maybe you don't want to wait the extra seconds it'll take to reprocess the whole PDF file. Just click the "Publish metadata only" checkbox and your update will be live in a second or two.

As long as you don't need to update the underlying PDF, the feature works for changes to any metadata field…tags, keywords, abstracts or any custom field you've added. And if you want to apply it to many documents at once, you can use it in batch operations from the main documents list…in which case those seconds can really add up!

Now, what if your homepage features a listing of latest updates? Normally, it's handy that Tizra automatically adds new reports whenever you publish them, with the newest at the top. But if all that's new about what you're publishing is that the name isn't misspelled anymore, maybe you don't want it bumped back up the list. Just click the "Don't update publication date" box before you click "Publish" and the fix goes in quietly.

Especially nice for RSS subscribers, who won't be bothered with alerts for a "new" publication that's really just a minor tweak!

Comments

Popular posts from this blog

Technical Podcasts

If there is something the web as surely changed, it was the way that software engineers need to work. It is now a crucial aspect of our work to be able draw from the huge internet knowledge base out there in an efficient way to get to the right answers. Part of that information extraction is related to the keeping-up-to-date effort that every developer is required to accomplish to continue to be productive. While previous a software engineer could rely mostly on print material, nowadays we need to rely as well on content available on the net. Podcasts are such a source that can bring an amazing amount of information to the mix of knowledge one needs these days. If you are a software engineer and have not jumped into the podcast wagon yet, I suggest you do so. Here is a list some technical podcasts that we hear at Tizra: The Java Posse : a fantastic podcast on Java development. Containing news info update, analysis of tools, overall software development discussions. Software as She Dev...

Using XML to Create a Better Online Reading Experience for the American Payroll Association

Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra!  Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at  Scribe  did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...

The importance of continuous integration

Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration ), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons: It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence ...