meshO Manager

Appearance

Club Registry ​

Audience: Event organisers maintaining the shared list of clubs across events.

The Club Registry is meshO Manager's master list of clubs, shared by every event on this server. Enter a club once — its name, short name, and logo — and it's recognised in every future event, so competitors' club details and logos stay consistent without re-typing.

It's one of the pages under Settings → Global registry, alongside the Competitor Registry and the Hire card registry.

A new installation doesn't start empty: Manager comes with a list of clubs, short names and logos already filled in, copied into the registry the first time it runs. From then on the registry is yours — later updates never replace it.

Why clubs are global ​

Clubs live in the registry, not inside a single event. Enter "Red Roos" once and every future event recognises it, with the same short name and logo. Each event keeps its own copy of the clubs its competitors use, merged on top of the shared registry — so a tweak you make for one event doesn't leak into the others. Because of this, you add and edit clubs here, not on an event's Clubs page. See Competitors, clubs and teams.

A country added later still reaches your events. If an event already has a club that had no country (or no organisation type) when it was added, it picks one up as soon as the registry has it. That happens when you save the club here, when an Eventor refresh brings it in, when you open the event, and when it's started or resumed. This only ever fills a blank: a country the event already holds is left alone, even if the registry now says something different. Events dated before today, and events that are complete or abandoned, are left exactly as they were published.

Open the Club Registry ​

In Settings, under Global registry, choose Club registry. The count beside the search box shows how many clubs the registry holds (Showing 4 of 536 while a search narrows it).

What's in the list ​

ColumnNotes
LogoThe club's logo, shown on result screens.
ClubFull club name. Click it to edit the club.
Short nameThe abbreviated name used where space is tight.
CountryThree-letter country code (ISO 3166-1 alpha-3, for example AUS).
External IDThe club's number in the system it's registered with — for a club from Eventor, its Eventor organisation number. Blank for a club Eventor doesn't know.
ProviderWho gave the club that number: Eventor, or blank.

Drag a column heading by its grip to reorder the columns, and use the Columns menu to hide the ones you don't need.

Why External ID matters. When you upload results or a start list to Eventor (or send it an IOF XML file), meshO includes a club's ID only when its provider is Eventor. Eventor credits a result to whichever organisation that number belongs to and never matches a club by name. So a school or club Eventor doesn't know is sent by name alone, and its runners' results are accepted without being linked to any club, rather than being credited to an unrelated club that happens to have the same number.

Use Search clubs to filter by full or short name.

Add and edit clubs ​

From the Actions menu:

  • Add club… — enter the club's name, short name, and country.
  • Clear club registry… — removes every club from the registry, after you confirm. Events keep their own clubs, and the short names and logos you set are remembered for when a club comes back (for example after the next Eventor refresh). This can't be undone.

Click a club's name to open Edit club, where you can change its Short name (required), Country, External ID, ID provider and Club logo, or delete it. Deleting a club from the registry doesn't affect any event.

Linking a club to Eventor. If a school or club you added yourself has since joined Eventor, enter its Eventor organisation number as External ID and Eventor as ID provider. Events that hold the club and have no ID for it yet pick the link up. A club that came from Eventor keeps the number Eventor gave it; you can't change it here. Removing a link only affects events that add the club afterwards.

Clubs an import meets. When a CSV or IOF XML entry list names a club the registry doesn't know, meshO adds it here as one of your own clubs, so next year's event recognises it by name. A club number in a spreadsheet is never treated as an Eventor organisation number unless Eventor gave that number to a club with the same name.

To set your own logo, choose a file under Override with a local PNG (max 256x256): it must be a PNG no larger than 256 × 256 pixels, and a preview shows it before you save. With Eventor switched on, Refresh from Eventor in the same dialog fetches that one club's logo again — replacing a logo you uploaded, so it goes back to Eventor's.

Populate from Eventor ​

If you use Eventor, the Actions menu can fill the registry for you. Both items appear only once Enable Eventor is switched on and the connection is set up under Settings → Eventor (see Settings):

  • Refresh clubs from Eventor — replaces the list with the clubs Eventor knows for the Organisation ID in your Eventor settings, and reports how many it loaded. A short name you changed by hand is kept, and so is every club you added yourself or that an import added.
  • Fetch default logos from Eventor — download each club's logo. A progress bar shows how many have been fetched. A logo you uploaded yourself is never replaced.

Tip: A club's short name is what most screens display, so set it to something that reads well at a glance — and upload a logo if you want the club's icon to appear alongside results.