HeraldicArt.org: Traceable Art | Emblazons | Blog

O&A Search for Unregistered OSCAR Submissions

Here’s a nifty trick for the folks who might be running their own O&A server — which is admittedly a very, very small audience.

The OSCAR software can generate a supplementary data file in the same format as oanda.db which contains the names and armory currently in-process on LoIs which have not yet made it to an LoAR.

Continue reading “O&A Search for Unregistered OSCAR Submissions”

A Concordance of Heraldic Terminology

TL;DR: The International Heraldry Phrasebook provides translations of 500 blazon terms between six different languages.

When reviewing documents about medieval and early-modern European armory, it’s quite common to encounter blazons in languages other than English. In some cases, automated translation tools such as Google’s will suffice, but the degree of specialized heraldic jargon sometimes exceeds their grasp, or yields a confusing jumble that doesn’t resemble a workable blazon.

In the middle of the last century, the short book Vocabulaire-Atlas Heraldic, by Gaston Ferdinand Laurent Stalins, attempted to address a similar need by providing a concordance of over 500 terms, showing their equivalents in each of English, French, German, Spanish, Italian, and Dutch, along with corresponding illustrations.

Continue reading “A Concordance of Heraldic Terminology”

Descriptions for Field Division Directions

Following the 2021 rules change, SENA A5F1b now says that that changing the direction of partition lines is considered a Substantial Change, as is the difference between divided and undivided fields.

As a result, when using the Complex Search form to do conflict checking for fielded armory, we can add a second line for the field that matches anything with a similar direction. Continue reading “Descriptions for Field Division Directions”

JSON Data for the Traceable Art

As part of my effort to facilitate the development of a successor to the current, somewhat jury-rigged system used to publish the Traceable Heraldic Art collection, I’ve been working on exporting the current data in a format that could be imported by someone developing a successor system.

You can now retrieve nearly all of the textual content of the collection via a series of JSON data files which are automatically rebuilt each time the site is updated. Continue reading “JSON Data for the Traceable Art”

Seeking A Technical Collaborator or Successor for the Traceable Heraldic Art

As we approach the fifth anniversary of my Traceable Heraldic Art project, and given how terribly overcommitted I am with numerous projects underway, I wanted to let folks know that if someone with a strong software-development background was interested in developing the next generation of the system that hosts that collection, I’d be open to collaboration and eventually turning it over to someone else to run.

This recent blog post lays out some of the background on how the current system works and what I hope might some day replace it, and links to the source code and data files I use to build and update the site. A successor system might be coded very differently, but I would hope that it would still support the current functionality and enable the development of new capabilities, so it seems likely to be of similar complexity.

This doesn’t mean I am about to abandon the project, but I have spent somewhere about four thousand hours on it already, and would like to free up some time to work on other things. If you’re a combination web-development nerd and armorial-art nerd, and you’re interested in spending years of your life improving and maintaining a much-valued community resource, drop me a line!

An Idiosyncratic System for Publishing the Traceable Heraldic Art

[Note: The below is a lightly-edited revision of an email message I sent to a contributor to the Traceable Heraldic Art collection who asked about the technology used to update the web site. It’s somewhat rambling and may not be of interest to most, but I figured it was worth putting it in the public record. — Mathghamhain]

In hindsight it would have been sensible to tackle the creation of the online Traceable Heraldic Art collection as a web database project, but for historical reasons that’s not at all how it’s architected. Continue reading “An Idiosyncratic System for Publishing the Traceable Heraldic Art”

On Belling the Cat

[Note: this post is not specifically related to heraldry, but I’ve included it here because it is very much concerned with the question of developing web-based tools and addresses issues that frequently arise in the discussion of digital heraldic resources. — Mathghamhain]

Someone recently commented that it was a shame that the SCA didn’t have a tool on its main website that allowed people to enter their zip code and get links to their their closest local branches — instead newcomers need to use a two-step process of using the SCA’s site to find a kingdom based on state, province, or country, then using that kingdom’s search tools to find their local group — surely it would be more welcoming to simplify that process? And might the fact that such an integrated tool doesn’t exist reveal that the SCA doesn’t care about newcomers?

As I responded, I realized that I had written similar comments about a number of other such proposals — frequent topics of this kind of discussion in the context of the College of Arms are building new web tools for Orders of Precedence, or a central registry of all coats of arms — and of course the same issue comes up in numerous other areas — so I figured I’d clip them out and post them here (with just a bit of editing to allow them to make sense on their own) for use the next time this kind of thing comes up.

One minor challenge for the “just enter your zip code” plan is that some parts of the world don’t use zip codes, so now you are building a web tool that uses country names, zip codes, Canadian FSAs, Australian post codes, New Zealand telephone prefixes, and I’m not sure what else, with an authenticated back-end interface for the officers who manage this data in each kingdom to send you updates, and you need to staff the administration and maintenance of this tool for the next decade, keep up to date with the changes in local officers and revisions to the SCA’s overall web design, and you have zero budget aside from free hosting on the SCA’s server (and that only if you use the tools and platforms they already support).

When you say “it might be time consuming” you are answering the question about why such a thing does not already exist — it would require a lot of work from each of a lot of unpaid volunteers, which would need to be sustained over a period of years to ensure it did not fall out of date. If someone qualified wants to tackle the project, I would love to see it done, but it’s a larger project than it might seem at first glance.

Projects like this are hard to solve with grunt labor — they require technical skill, long-term dedication, and team-building. This is why we haven’t (yet!) solved this problem.

If you can recruit a talented software developer with strong communications skills who wants to devote thousands of hours to this project, I’d be excited to see the results!

And if you are an experienced technology professional who wants to volunteer a decade of their life to building this and keeping it running, please step forward — this would be a great project!

But if what you are saying is that someone else should do this work, about which you lack sufficient knowledge to be able to formulate an implementation plan or estimate the scope of effort required, consider the fable of Belling the Cat.

Conflict Checking Multiply-Divided Field-Only Armory

A couple of years ago, I posted about a technique I picked up from Marie de Blois that allows conflict-checking two- and four-part field-only armory with the O&A complex search form.

It entails running a search for the line type, plus each of the tinctures, and for the tinctures together in reverse order, and the codes for field-only and peripheral-only. Continue reading “Conflict Checking Multiply-Divided Field-Only Armory”