Wormholes

I want to share, but...

You are basically done with three folders: wormholes / sites / warp-in
Obviously you can delete the whole wormhole folder whenever you fold your home, same for sites. Warp-in can well be split into different stuff like assets, hostile assets, salvage, safes etc.
For the naming convention of wormholes, I suggest you just name them similiar to c2a, c2b and so on, mark the wormhole towards your home system with a dot in front and you're mostly done. So give every wormhole a unique identifier and draw youself a map (pen&paper if necessary)
So wormholes (this case you sit inside c2a, so the first c2 in the outgoing chain from your wormhole, as example) -
.c2a → home
c4a
lowsec A

and so on. I believe mostly anyone should be able to find all the things necessary. Increase the index as you find more systems of the same class :)

Hope that helps, afaik wormhole corps tend to organize their wormholes like that or similiar, with some corps taking cryptic letters for confusion issues (like calling chains R1, T1 etc., not necessary unless you got multiple wormholes)

regards

Thank you both for your comments.

I heard of siggy but i m a bit greedy to spend ISK on such tools :)

If you want to host and develop a mapping tool yourself then this one is really good, and I believe its the one lanyaie is referring to:
W-Space Alpha

They also set up a site with the alpha version that can be used. I'm not sure about the lifetime of that site though so check with them before getting too attached to it.

Ouch, you make my brain hurt.

Living deep in a C4 our chains can get quite extensive, yet we basically use just 3 folders

Home sigs
Home anoms
Chains

Everything related to our home system goes there. Everything else goes in chains.

First we only use the letter portion of a sig name. It keeps it shorter and the letters are all unique, so the 3 numbers are redundant.

For wormholes we match them up.

So for example, if our home static is:

VCX x877 2300 (sig id, WH designation, time activated).

When we reach the other side we bookmark the other side:

(VCX) k162 J??????

If you sort your sigs by distance, the sigs in the current system always show on top. So even if our "chains" folder has lots of locations, the current system sigs are always at the top.

We also map these using wormhole space. It is free and you can host it yourself if you want.

http://wh-space.wiadvice.com

Where did anyone say they weren't using corp bookmarks?

Just on that point, i've had the letters cycle back in a day, and have the same letters, with different numbers. Was a bit confusing at first, thought i had marked it down wrong. I had something like RFU-349 at DT, then RFU-256 12 hours later. It's only happened the once, but i'm sure it is possible.

Keep It Simple!
Easiest way for everyone, including the scanner is using a mapping tool and naming your wormholes :
examples:

where you are-> where it goes

Home>C5a and the other side C5a>home
C5a>C5b ...

If you have an extra chain add numbers :
Home>C5.1
C3.1>c3.2...

It is the mapping tools that helps you to know where to go, there you also set what the hole name is right now, like c5a, c3c,.. .
Adding a dot to the way back also helps.

Best is not to use the j-number it is just to long to type.
Before the corp bm's and before ducks we had this system:
J111111>j222222 H296 (crit at 25:00 Eve time)
It takes to long to type and it isn't easy to maintain this type of naming in long scanning sessions.

Well... I'll tell you what works for us.

First of all, the easy part.

When we jump out of our WH, then the Exit back into our WH is called

Wormhole >> Home

Moreover, the deeper you go down the rabbit hole, each exit back in the direction of home is called "Wormhole >> Home" as you jump through.

So every exit in the direction of home is marked like this--including entrances from K space--so you don't have to worry about where you are.... just follow the in space bookmarks to "Wormhole >> Home" and like following a trail of breadcrums, that's where you always end up.

Exits to K space are marked as follows

XXXX >> (Lowsec)
XXXX >> (Highsec)
XXXX >> (Nullsec)

The XXXX is the name of the exit, like U210, K162, or whatever. In our case we don't usually care WHERE it comes out, just what kind of exit it has.

Exits from one wormhole into another WH are marked like

XXXX >> (Class - static)

So for example, a K162 into a C4 with a C3 static is called

K162 >> (C4-C3)

If there is more than one K162 into a neighbouring wormhole then they are just marked

K162a >> (class-static)
K162b >> (class-static)

and so forth.

if a wormhole has a more than one static then one of them will be a static to K space so that's the one that gets marked. The fact that it has more than one static is indicated as follows

K162 >> (C3-Lowsec*)

The * meaning that it has more than one static.

We don't make maps anymore. With this simple notation we can find our way around just fine.

Uh, what? No...sigs that were in a system at DT will have the same 3 letters.

Now see this is where i feel the opposite. Having the sig ID's makes it easier to keep track of new and existing bookmarks.

After downtime I just scan the existing bookmarks and update their sig to match the new ones.

That way if new sigs appear during the day, it becomes easy to know which ones have already been scanned.

Say there is one WH after downtime. A few hours later another corpie comes in and sees a new sig. By comparing the ID's in the locations list he knows already which have been scanned and which are new. If yet more sigs spawn later in the day you can keep track of which have been taken care of.

Otherwise each person who comes in after someone else has to go through the task of re-verifying which sigs have been scanned and which are new.