This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Migrating from SplashID to 1Password
TranceMist
Junior Member ✭
in Mac
<div class="IPBDescription">Addressing design differences between the two, not just import</div>Other topics have addressed import issues, I'd like to address a more architectural issue in moving from SplashID to 1Password...
I've been holding off importing my almost 1200 entries in SlpashID into 1Password because there just simply does not appear to be an automated way to import what has been a very carefully hand crafted database thus far and maintain the integrity.
So I've come to accept the fact that I will have to move these entries manually.
The missing link for me is that there is not a 1:1 functionality mapping between SplashID and 1Password.
In SplashID I can effectively define my own 9 fields for each type.
In 1Password, for most of my web logins I'm forced to either use the Logins type or the Secure Notes type. Neither seems to provide adequate structure.
These have the following issues:
Logins: Where do I enter the answers to the three secrets the web site wants to ask me?
The Logins form is not compatible with this. If I put them in there (i.e. manually create the fields), it can be overwritten by SplashID.
Yet I need to keep track of those things in the same context as the web site, I don't want to have a total of four 1Password logins items for one web site!
Secure Notes: Just plain text, there's no way to organize anything. unstructured.
I want to be able to keep track of the login, password, email address used, all of the secrets, perhaps what date of birth I gave it, etc.
I want to be able to keep everything put the first two updated manually (because there's not a good way to automate this), and be assured it won't be overwritten.
The best solution I can think of is just to allow me to create my own fields or my own form using the Accounts type within 1Password, but alas there does not appear to be a way to customize Accounts.
Another solution might be to keep all of this information in the freeform notes section of the Logins entry, that feels unstructured and kludgy.
Any suggestions on how to approach this problem?
I've been holding off importing my almost 1200 entries in SlpashID into 1Password because there just simply does not appear to be an automated way to import what has been a very carefully hand crafted database thus far and maintain the integrity.
So I've come to accept the fact that I will have to move these entries manually.
The missing link for me is that there is not a 1:1 functionality mapping between SplashID and 1Password.
In SplashID I can effectively define my own 9 fields for each type.
In 1Password, for most of my web logins I'm forced to either use the Logins type or the Secure Notes type. Neither seems to provide adequate structure.
These have the following issues:
Logins: Where do I enter the answers to the three secrets the web site wants to ask me?
The Logins form is not compatible with this. If I put them in there (i.e. manually create the fields), it can be overwritten by SplashID.
Yet I need to keep track of those things in the same context as the web site, I don't want to have a total of four 1Password logins items for one web site!
Secure Notes: Just plain text, there's no way to organize anything. unstructured.
I want to be able to keep track of the login, password, email address used, all of the secrets, perhaps what date of birth I gave it, etc.
I want to be able to keep everything put the first two updated manually (because there's not a good way to automate this), and be assured it won't be overwritten.
The best solution I can think of is just to allow me to create my own fields or my own form using the Accounts type within 1Password, but alas there does not appear to be a way to customize Accounts.
Another solution might be to keep all of this information in the freeform notes section of the Logins entry, that feels unstructured and kludgy.
Any suggestions on how to approach this problem?
Flag
0
Comments
-
[quote]The missing link for me is that there is not a 1:1 functionality mapping between SplashID and 1Password.[/quote]
This is, unfortunately, true of nearly all imports regardless of application or format. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_worried.png' class='bbc_emoticon' alt=':S' /> It pains all of us. We wish it was easier, and we are always striving to make it so. That said, I would love to offer some practical tips, and perhaps some other users can contribute their own tips as well.
[quote]Logins: Where do I enter the answers to the three secrets the web site wants to ask me?[/quote]
I store them in the Notes field.
[quote]Secure Notes: Just plain text, there's no way to organize anything. unstructured.[/quote]
We prefer the term freeform. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' /> It's a great way to store sensitive prose that isn't formatted into neat little nuggets like a story you are working on, a gift list, or whatever you like.
That said, we are all looking forward to custom templates which will alleviate your concerns. I don't have a time frame for a specific release, but this is something we are excited to offer in the future.
If we can be of further assistance, please let us know.
We are always here to help!Flag 0 -
[quote name='TranceMist' timestamp='1303400896' post='25319']
The best solution I can think of is just to allow me to create my own fields or my own form using the Accounts type within 1Password, but alas there does not appear to be a way to customize Accounts.
[/quote]
I don't have any personal experience with SplashID, so maybe someone who has can chime in. But you've hit the nail right on the head there, Trance. This has been talked about for some time. There are a few key obstacles to this:
[list]
[*]1Password has to understand fields well enough to know what to do with them.
[*]1Password has to be architected in a certain way to support this functionality.
[*]Adding this ability without adding a way for 1Password to somehow "learn" how to use user-defined fields would result in a number of people being unhappy when 1Password [i]didn't[/i] know what to do with the additional data.
[/list]
What 1Password does, it does really well, in my opinion (although there is always room for improvement!) But getting there meant being picky about what it does so that it can excel at its core functionality. I think that tacking on a way to add user-defined item and field types without making it functional and really useful to people would be worse than if we never added these features at all. While you and I might be satisfied to just make all kinds of crazy fields for our data, I suspect that the vast majority would be chagrined to discover that -- after painstakingly customizing their Login items, for example -- there was nothing for them to actually do with the additional data.
[quote]
Logins: Where do I enter the answers to the three secrets the web site wants to ask me?
[b]The Logins form is not compatible with this. If I put them in there (i.e. manually create the fields), it can be overwritten by SplashID.[/b]
Yet I need to keep track of those things in the same context as the web site, I don't want to have a total of four 1Password logins items for one web site!
[/quote]
I guess I am a little confused by this. Are you somehow sharing data between 1Password and SplashID?
As far as Login items for sites with multi-step login processes, as long as the field names do not overlap, you can actually consolidate these: Try manually saving each step in the process, creating a new Login item each time. If the fields names are different (i.e. "username," "password," "question1," etc.), you can merge them all into a single Login item manually, which will simplify your login process.
Unfortunately, it is not always this easy. My bank's login process uses "password" designations for fields on each page, and 1Password does not support multiple identical fields, because then it would not know what to fill.
[quote]
Another solution might be to keep all of this information in the freeform notes section of the Logins entry, that feels unstructured and kludgy.
[/quote]
It is absolutely a kludge, and believe me: we are very conscious of this. I am sorry that we don't have a better solution to offer you at this time, but we want to make sure that when we do offer one it is the right one, and it works beautifully for everybody. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />Flag 0
