Calling names, hygiene, and other grooming matters

(on the good use of bookmarks)

Calling names.

As one's BM library grows, the need to organize them does, even more so if traveling a lot and using a Navigation window.

The naming scheme described below was designed with Navigation window use in mind, and will prove ill-adapted to right-clickers because of the length of the labels it generates - and how they may be truncated by the right-click menu.

Basically, it goes like this:

For insta-BMs:

{SystemName}: {Origin} -> {Destination}

For locations:

{SystemName}: {Location} - {Attributes}

Examples:

Insta-BM from Jita Gate to Kemerk Gate in the Niyabainen system:

Niyabainen: Jita G -> Kemerk G

Insta-BM from Jita Gate to Niyabainen IX - Moon 4 - Expert Housing Production Plant:

Niyabainen 9: Jita G -> M4, Expert Housing

[UPDATE]
An important change got introduced with NWO, as all stations' sizes were changed so that no station bubble is smaller than 45kms in diameter anymore.
The direct implication is that any BM set to the dead center (or close enough) of a station will now work from any warp-in vector.
The above example, provided the BM was set properly (post NWO), would look like this, basically ignoring the origin part as irrelevant.

Niyabainen 9: 00 -> M4, Expert Housing

...be wary of renaming old "Gate to Station" bookmarks according to this model, though, as they might have been set to coordinates that differ from the current center of the station and could prove unreliable: you're usually faster done setting up new BMs when as you go for stations, as the new gigantic size of stations makes that super easy and quick.
[/UPDATE]

The corresponding return trip from Niyabainen IX - Moon 4 - Expert Housing Production Plant to Jita Gate:

Niyabainen 9: -> Jita G

This label is noticeably shorter because the return trip to the gate doesn't have to specify the station as its Origin: any object orbiting Niyabainen IX will use the same insta-BM to reach Jita G.
An insta-BM from Niyabainen IX - Moon 4 - Expert Housing Production Plant to Perimeter Gate would be slightly different, because the Perimeter Gate is very close to Niyabainen IX:

Niyabainen 9: M4 -> Perimeter G

The general idea is to qualify in-system locales based on Destination, not origin, since most people know where they come from and care about where they go.
A notable exception is Location -> Gate insta-BMs, where the number (Index) that comes right after the current system name is relative to Origin.
The idea is that, when listing by label, all the gate-to-gate insta-BMs for a given system will be grouped apart from the other BMs.
In practical terms, when travelling, one just has to scroll to the end of the relevant system BMs to find all gate-to-gate insta-BMs.
Below is a list of the possible types of BMs, with examples, from 'wider' to 'closer'

Cross-system BMs:

These are the usual instawarp BMs that get you right within activation range of an object. Nuff said.

Gate -> gate:

{SystemName}: {OriginGate} G -> {DestinationGate} G
Niyabainen: Kemerk G -> Jita G

Location -> Gate

{SystemName} {OriginPlanet#}: M{OriginMoon#} -> {DestinationGate} G
Niyabainen 9: -> Jita G
Niyabainen 9: M4 -> Perimeter G

Gate -> Location

{SystemName} {DestinationPlanet#}: {OriginGate} G -> {DestinationPlanet#},M{DestinationMoon#}, {DestinationNameShort}
Niyabainen 9: Jita G -> M4, Expert Housing

Location -> Location (different planets)

{SystemName} {DestinationPlanet#}: {OriginPlanet#} -> {DestinationPlanet#}.M{DestinationMoon#}, {DestinationNameShort}
Foo 9: 5 -> 9.M12, StripClub Inc

Location -> Location (same planet, different moons)

{SystemName} {Planet#}: M{OriginMoon#} -> M{DestinationMoon#}, {DestinationNameShort}
Foo 9: M7, Crackers Bakery -> M12, StripClub Inc

Location -> Location (same moon)

{SystemName} {Planet#}: M{Moon#}, {OriginNameShort} -> M{Moon#}, {DestinationNameShort}
{DestinationNameShort}
Foo 9: M7, Crackers Bakery -> M7, BigMouth Diner

Locations:

Location names are use to BM a Station, POI or anchored item, but also enter in the construction of insta-BMs names, as can be seen above. The 'NameShort' handle means that the trailing parts of the name (usually whatever comes after the owning corp name) are stripped, since they usually aren't required for proper identification. As usual, common sense - if available - shoudl be used.

Stations

{SystemName} {Planet#}: M{Moon#} - {StationNameShort} - {Attributes}
Niyabainen 9: M4, Expert Housing - NAGA Shop

Belts (and items)

{SystemName} {Planet#}: B{Belt#} - {ItemNameShort}
Niyabainen 8: B4
Niyabainen 9: B3 - MinerCan 1

Beacons (and other POIs)

{SystemName} {Planet#}: {ItemNameShort} ({Attributes})
Vuorrassi: R-Drone Infestation (3/10)
Niyabainen 9: B3 - MinerCan 1

A library of BMs built by this naming system and used with a Navigation window requires slightly more effort to set up than a randomly throwed-together bunch of BMs, but the ROI is insanely high, as it will save both time and effort, especially in circumstances where time and accuracy are critical.
Combined with the new multi-copy ability of BMs in Exodus, it allows for easy management of large collections of BMs, plus if you really want numbered routes (and while I whish you a long and interesting life in this case) you can just copy the pack of required BMs to a new MyRoute folder and replace the system names by numbers.

TTFN,

Elroy Cruise