Forum Posts Feed
MyInfo 3.59 released
< Next Topic | Back to topic list | Previous Topic >
Posted by Jan Rifkinson
Jan 17, 2007 at 03:12 PM
I’ve revisited MyInfo & think it is an interesting program that has made quantum jumps in development since the last time I trialed it.
IMO current version is quite talented & v4—w substantial list of new options—is due out q2 of 2007. Current version seems pretty stable.
Tech support/developer comments/help is commendable. Ongoing development seems serious as company has been around for a while. IMO, it’s definitely worth a look see if you are looking for this kind of data handler.
Unless something very weird happens I am seriously considering migration (don’t know how yet) from ADM to MyInfo when v4 appears.
This has raised an interesting problem. Data handlers have two basic problems: getting the data in & getting the data out, i.e. once the user commits to one data gatherer, it is sometimes very difficult to migrate to another program. Very frustrating.
—
Jan Rifkinson
Ridgefield, CT USA
Posted by Derek Cornish
Jan 17, 2007 at 07:31 PM
Jan,
What features of MyInfo particularly attract your interest? I found the ability to import .HEAD files interesting, but could never find much of a use for it. In other respects I found WhizFolders a more attractive proposition, though I ended up buying neither - maybe because I use Zoot so much. Where or how does MyInfo feature in your workflow?
Derek
Posted by Stephen Zeoli
Jan 17, 2007 at 09:18 PM
I use MyInfo to complement Zoot. We all know Zoot’s limitations, and MyInfo handles those tasks that Zoot can’t fairly well. Here are some of the features of MI that I especially appreciate:
1. Drag any document into the tree and it creates an info item and stores the document in its own database. This is useful for me, because I receive a lot of price quotes as PDF attachments to e-mail. Rather than worry about where to save them, I can just drag them into MI and drop them under the project heading with other information about the project.
2. Multiple databases open at the same time and accessible through tabs.
3. Cross-database searches.
4. Completely customizable columns that accept various types of metadata.
5. Tagging of info items with keywords, for an additional layer of categorization.
6. Pretty good OLE integration.
7. Continual improvements—the developers do not rest on their laurels.
These charateristics are not unique, but they are implemented in a nice, clean interface that doesn’t get in the way of work.
For me, MI is the PIM I use for project management and for collecting that data that Zoot isn’t good at.
Steve Z.
Derek Cornish wrote:
>MyInfo feature in your workflow?
Posted by Daly de Gagne
Jan 17, 2007 at 11:49 PM
Steve, that’s a pretty good overview of MI’s features. Last week I wrote that I amusing MI and WhizFolders. I am liking both, but if MI allowed multiple open windows I would give up WhizFolders.
MI, in addition to multiple open windows lacks a hoisting ability, and the ability to have more than one set of columns for a specific file. ADM has both these features. The value of hoisting is self-evident. The value of being able to use more than one set of columns is that if, within the same outline, you have info requiring different types of metadata, you can do it. Otherwise you have to seperate the info into different files which, from a functional perspective may not make sense.
MI’s plans for version 4 look good, except I saw no reference to hoisting or multiple windows.
The continuing frustration for some of us is the question marks around ADM. In terms of features and concepts it is quite advanced; but until there is a really solid and market-ready version 4 I am not confident about the program’s future.
Daly
Stephen Zeoli wrote:
>I use MyInfo to complement Zoot. We all know Zoot’s limitations, and MyInfo handles
>those tasks that Zoot can’t fairly well. Here are some of the features of MI that I
>especially appreciate:
>
>1. Drag any document into the tree and it creates an info
>item and stores the document in its own database. This is useful for me, because I
>receive a lot of price quotes as PDF attachments to e-mail. Rather than worry about
>where to save them, I can just drag them into MI and drop them under the project heading
>with other information about the project.
>
>2. Multiple databases open at the same
>time and accessible through tabs.
>
>3. Cross-database searches.
>
>4. Completely
>customizable columns that accept various types of metadata.
>
>5. Tagging of info
>items with keywords, for an additional layer of categorization.
>
>6. Pretty good OLE
>integration.
>
>7. Continual improvements—the developers do not rest on their
>laurels.
>
>These charateristics are not unique, but they are implemented in a nice,
>clean interface that doesn’t get in the way of work.
>
>For me, MI is the PIM I use for
>project management and for collecting that data that Zoot isn’t good at.
>
>Steve
>Z.
>
>
>Derek Cornish wrote:
>>MyInfo feature in your workflow?
>
Posted by Stephen Zeoli
Jan 18, 2007 at 02:11 PM
Daly,
Regarding the lack of hoisting in MI, I agree that that would be a great feature. In some ways, however, MI mitigates that issue with its multiple open databases, and cross-database searches. What I mean is that hoisting is important in a large database when you want to focus on a single topic. In MI you can just create a database for that topic, but still have instant access to it through its tab and can find information within that topic through a cross-database search. I’m not saying this is ideal, just that it is less important to have hoisting in MI as it would be in a program that didn’t allow for cross database searches.
Steve Z.