Category talk:CoA Lab

Tools for tagging and categorizing

After some major changes, expansions and new developed possibilities, much of the handling has become easier — but it may need some knowledge to use it in an optimal manner.

Most work can be done as until now !

Just a few things look a bit different, and to use new options it may be necessary to know about.

There I try to describe in short the best processing, and I'm gladful to answer all questions swiftly; just ping me.

0A longer description including all details can be seen at Category talk:Graphic Lab#The flow0

Everything can be done a lot of different ways, the one I would recommend is:

• When a coat of arms-image is not yet converted to COAInformation, it should be done with the script.

It works as well for SVG as for (the relatively few remaining) raster images. All files will get the tincture parameter,

and (currently only SVG files) also the image parameter. When the script has ready done, it displays the file description page in edit mode.

• When file descriptions had been already converted to COAInformation earlier, the can be opened fo editing, and it is the same situation as above.

Depending on the options set in the User:commons.js (or another skin) in edit mode for SVG files two entry options for /simpleSVGcheck.js exist,

the icon above, or the "■ → SVG Igen" link left. Before using it, the whole "image" line of any eventually previous validation should be removed.

The script will not only perform the W3C-validation but also a lot of formatting cleanup. It will create the parameters for COAInformation depending on the situation.

This may depend on whether the user who is the author of the file ( the 'artist') is present in an intern table where his options are predefined.

Many users who created a certain number of coa files have an entry in this table, amd it is not a problem to insert more users when the need exists.

These user-specific presettings are accessed with a short key. One user may have more presettings, e.g. for coas, elements and ecclesiasticals.

The predefinitions comprise

1. the drawing tool (Inkscape, Adobe or whatsever) normally used
2. the W3C error count is normally preset with zero
3. the topic is either for CoA, CoA-element or ecclesiastical CoA
4. a (national) graphic lab can be preset when the user belongs to it
5. definitions for subcategorizing are user-specific
6. different possibilities for editing the validation box may be preset
7. user_categories can also be predefined

All the presettings can be modified before publishing the edit.

Of course it is always recommended to check the output of the script, and to perform a preview before publishing, when in doubt.

For the relatively few raster images exists not (yet) such an automatic comfort; the key has to be set manually, but a minor cleanup

script can be used, with the "■ cleanup JS" link left. See e.g. Armoiries Haute-Lusace.png or Blason ville fr VersSelle (Somme).png

Information tables can be seen at Category talk:CoA Lab-fr or Category talk:CoA Lab-ch.

When you need more detailed information, or about a specific part, add your questions with a ping to me -- sarang♥사랑 13:55, 25 November 2022 (UTC)

---

User key table

For ordering and categorizing CoAs, a table is implemented where each CoA drawer has a two-letter key; all standard parameters can be stored there to avoid that they had to be specified explicitely in each single file again and again. Moreover, a change for all CoA-files of a user is done only once at this central place, and not in each one of hundreds of files.

Nevertheless all parameters can be modified for single files, when necessary. For example, when a user draws CoAs with Inkscape, but then draws one file with e.g. Illustrator or something else, its key with all the other parameters can still be used, with an added modification.
It occurs often that a user draws 'normal' CoAs and a few CoA elements - or SVG and raster CoAs; this may require modifications.

Because user-ids have a length between 3 and up to 30 bytes the id itself is not used, the short key will be enough in each file description, e.g. |image = TL
It sounds complicated (and it is!) but that automated processing simplifies drastically the editing of thousands of files.

Coats of Arms, elements and ecclesiasticals

Besides the "normal" CoAs are there also elements used for drawing vector image CoA, and the group of CoAs used by religious leaders of the Roman Catholic Church. Another differentiation exists for bitmap (raster image) CoAs.

These groups exist

• SVG CoA
• SVG CoA elements
• SVG ecclesiastical CoA
• SVG ecclesiastical CoA elements
• BMP CoA
• BMP CoA elements (rare)
• BMP ecclesiastical CoA
• BMP ecclesiastical CoA elements (rare)

and they need a special treatment by description and categorization. The third image-parm for elements is "ce", for ecclesiasticals "eh".
Either this parameter is entered as a modification, or another user-key is defined with it. In theory, up to 8 user-keys can be defined,
but when a user does not have many drawings of a group it seems better to treat it with modifications.

Example: a (hypothetical) user key "Uu" is specified with all needed attributes.

• The main key "Uu" has the third parameter "c" specified for 'normal' CoAs.
• An other key "Uuc" (c for charges) may be defined for elements - or the main key is used with 'ce'.
• An other key "Uue" (e for eccles.) may be defined for ecclesiasticals - or the main key is used with 'eh'.
• An other key "Uux" (x for raster) may be defined for 'normal' raster CoAs - or the main key is used with modifications.