This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Import into "Software"
Comments
-
I have recently started using 1Password. I imported all of my "stuff" from Splash ID but a lot of it is in the wrong places. I have quite a bit of things that were software ID's and registrations with key codes that ended up as Logins in 1Password. I don't see an easy way to change them. Is there one?Flag 0
-
Welcome to the forums, Jason and KMWAZ!
Jason, please put the name of the application in column 1, the version in column 2 and the license key in column 3. Then chose the LicenseKeeper format.
KMWAZ, I have merged your post with this thread since at this time it is only possible to import Logins, Secure Notes, and Software Licenses (using the above technique).
Importing is one of the more difficult aspects of software development since half of the equation (the exported file) is completely beyond our control.
I hope that helps, though, if even a little bit. Please let me know.
Cheers,Flag 0 -
Hm. I am not able to reproduce the issue. I just started with a fresh copy of SplashID, created two Web Logins and one Serial Number. I exported the file to CSV from SplashID (File > Export > CSV). Then, when I imported the CSV file into 1Password, the Serial Number was placed in 1Password's Software License vault and the Web Logins were placed in the Logins vault. My understanding is that SplashID allows for radical customization, so perhaps that may be having an impact here.
I have attached the sample CSV file I used to test. Please let me know if you get different results with it. I would love to figure out why the Software Licenses are not being filed correctly from a standard SplashID CSV file on your system if that is the case.Flag 0 -
[quote name='khad' timestamp='1302998193' post='25031']
…, when I imported the CSV file into 1Password, …[/quote]
Can you expand on that, e.g. did you choose the aforementioned LicenseKeeper format and which Character Encoding? With SplashID format and UTF-8 encoding imported SID Serial Number items end up having the same Title and Publisher from field 5 of the CSV instead of using field 2 for the Title. And none of SID custom fields that appear as 1P notes have SID field names, which often makes identification tough or impossible without referring back to SID.
Still [i]way[/i] too much information is lost or misplaced in 1P imports of SID exports for me to tackle migrating. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/sad.gif' class='bbc_emoticon' alt=':(' />
PS: Speaking of importing… opening a 1Password Interchange File while 1P is locked starts the import wizard that'll eventually fail.Flag 0 -
It really is tough, sjk. Custom…everything…in SplashID makes a 100% reliable import tricky.
I used the standard SplashID import format, but as you can see from the CSV file, I only had Serial Number and Publisher. It does appear that the Title I chose ("MySerialNumber") was not imported correctly and the Publisher ("Your Mom") was used as the Title instead (while also being imported as Publisher).
The custom fields are killer, but this does appear to be a bug. I will pass this along to the developers! Thanks for pressing the issue.
[quote]PS: Speaking of importing… opening a 1Password Interchange File while 1P is locked starts the import wizard that'll eventually fail.[/quote]
Hm. While the menu item (File > Import) is disabled, double-clicking a .1pif file in Finder does open 1Password. Perhaps we could give the warning earlier in the Import Assistant, but the unlock screen is clearly visible behind the Import Assistant window when the error is given:
[code]Exception: 1Password must be unlocked.[/code]Flag 0 -
Thanks for the feedback, Khad.
I remembered an exported SID CSV doesn't contain the custom field names so of course 1P won't know about 'em. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_blush.png' class='bbc_emoticon' alt=':oops:' />
Maybe a lost cause for me to keep pressing unless 1P's SplashID importer is eventually able to process SID vID exports containing all the necessary info for 1P to make improved use of. The vID format doesn't look particularly daunting to reverse engineer, especially considering (surprisingly!) .vid files are treated as CSV file by the [url=http://code.google.com/p/quicklook-csv/]QuickLook plugin for CSV files[/url] that QL displays in a quasi-interpretable way. And there's Doug Anderson's [url=http://forum.agile.ws/index.php?/topic/3142-splash-id-vid-importer/]Splash ID VID importer[/url] contribution to the effort (which I haven't tried, but could be more tempted to if all else fails).
Even if you've got all the info from SID there really aren't enough useful places to put it in 1P without expanded custom field support but at least it needn't go missing like with the current CSV export/import process.
You understand the .1pif opening vs. locked 1P issue I briefly mentioned that could be improved.Flag 0 -
I agree. There is certainly room for improvement. I am often nudging the devs on this one, but it really is a tough nut to crack. If we had a large pool of real-world SplashID files to test, that would help, but we certainly aren't going to be soliciting those any time soon for obvious security reasons. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />
Hopefully we can keep refining the process with these individual tweaks as they arise and will have it perfected soon enough.
Thanks again!Flag 0 -
Wow, Doug's SID vID importer script did an impressive job with importing +150 SID Serial Number items! The results are magnitudes better than with the bundled SplashID CSV importer; has AWS considered testing/integrating/including it as an alternative (at least for certain item types)? Makes decent use of available 1P Software item fields and retains other SID custom fields [i]and[/i] names in the notes. Unexpectedly, quite a few imported items have app icons. Puzzling where those came from since there's no data in the vID file, no URL for most of the items, and corresponding apps aren't necessarily installed. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/confused.png' class='bbc_emoticon' alt=':confused:' />
With an acceptable amount of cleanup these results could be tolerable enough to keep/use. Too bad at least the License Key and notes can't be masked since they often contain info I consider sensitive.
Thanks, Doug! (who mysteriously disappeared after making his first and only post with the script)Flag 0 -
I'm glad [url="http://forum.agile.ws/index.php?/topic/3142-splash-id-vid-importer/"]Doug's SplashID vID importer[/url] worked well for you. I just answered an email moments ago from a customer who also had very good results with it!
[quote]has AWS considered testing/integrating/including it as an alternative (at least for certain item types)?[/quote]
I can't speak for the developers, but anecdotally it does give impressive results.
[quote]and corresponding apps aren't necessarily installed.[/quote]
That's a real head-scratcher, but I wouldn't complain. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/laugh.gif' class='bbc_emoticon' alt=':lol:' />
[quote]With an acceptable amount of cleanup these results could be tolerable enough to keep/use. Too bad at least the License Key and notes can't be masked since they often contain info I consider sensitive.[/quote]
I am really hoping we can make this more flexible with the new data format, but I don't have any information I can share right now.
[quote]Thanks, Doug! (who mysteriously disappeared after making his first and only post with the script)[/quote]
Indeed. Thank you, Doug, wherever you are.Flag 0 -
I've more cleanly integrated SplashID vID format importing here:
[img]http://dl.dropbox.com/u/71730/AgileBits/SplashID%20vID%20%28Import%20Format%29.png[/img][img]http://dl.dropbox.com/u/71730/AgileBits/SplashID%20vID%20%28Step%201%29.png[/img]
When testing SID vID Web Login importing I had to select MacRoman as the character encoding; UTF-8 failed with a few parsing errors (didn't save 'em, knowing how to easily reproduce 'em).
Btw, some text in importer HTML files could be proofread/updated and out-of-date images (e.g. SplashID-Export.jpg) recaptured.Flag 0