English > Feature Suggestions

Default values

<< < (2/3) > >>

rick.ca:

--- Quote ---I have custom fields which values are same for large continuous groups of movies, but for each one by one I have to manually edit them and choose those values after importing/scanning
--- End quote ---

Okay, now let's assume we have an "edit bar" that can save searches and consider how that might work...

First, there's there's no difference in the efficiency of entering the default values before or after the movies are added. In the more general case, it would be safer and easier to apply values after—when you can see the records it's going to be applied to. I don't know if the new tool will do this, but it would be very helpful (again, in it's general use) if it could display a drop down of the unique values currently existing in the field for the selected records. This makes it much easier for changing values, and makes it more difficult to do so when the intent is to fill fields that should be empty. So if it worked that way, entering default values after the movie is added (and perhaps updated) would clearly win.

Second, being able to apply default values to a set of fields all at once might be helpful if a the same set of fields/default values is commonly used, and such sets can be saved and edited. I wonder if that's not a tall order for something not many users would need. But, more importantly, I don't think it would make all that much difference. The "edit bar" might even be more efficient, all things considered. Say a common use is like your example—you need to set four fields. The values for two of them (DVD Case # and Playlist) likely need to be updated from the last use anyway, so running those separately is no less efficient than changing the values in a saved configuration, then applying the edit. The default values for the other two may never change (I may not understand them, but it seems they would always be "true"), but that means they would be easy to pick off a drop-down list and applied. So I visualize being able to apply four separate edits using such a tool in less time than it would take to fiddle with some kind of default settings configuration, then apply the multi-edit.

Third, an equally likely scenario is that for a batch of movies the default values may not be all the same for a particular field, or some may not apply to all movies. The one-field-at-time approach is more versatile and allows such a task to be completed in whatever way is easiest for the user. That might be applying common values to all then changing those that should be different, or simply modifying the selection from field to field. This could be done with the other approach as well, but, again, would require the more cumbersome changing of the default settings for each iteration.

So while the "edit bar" may seem to be more work when there are multiple defaults to be set, I'm not convinced this is the case. Even if it is in some situations, I don't see how that can outweigh the advantages: It's easier to implement, versatile, and would be one easily understood tool that can used for a number of different purposes (e.g., MME, set default values, edit single field without having to put record in edit-mode).

buah:

--- Quote ---Third, an equally likely scenario is that for a batch of movies the default values may not be all the same for a particular field, or some may not apply to all movies.
--- End quote ---

My logic how to spare time is as follows:

If you have default values, than you'll have to change/correct those values (possibly) only for some of them after importing/scanning. If you don't have default values, unavoidably you'll have to set them all after importing/scanning.

patch:

--- Quote from: buah on June 25, 2010, 10:09:59 am ---If you have default values, than you'll have to change/correct those values (possibly) only for some of them after importing/scanning.
If you don't have default values, unavoidably you'll have to set them all after importing/scanning.

--- End quote ---
Agree that it would make sense for some fields where an almost always value applies, eg seen, language, quality, some custom fields. In other cases null is more appropriate. The harder question is does the utility justify the programming effort?

ps imo generalization of a multiple record field editor is a different topic.

rick.ca:

--- Quote from: buah on June 25, 2010, 10:09:59 am ---And, please keep in mind, that this idea came from my experience, not theory, since I haven't seen anyone here had more movies than me, meaning no one had more PVD clicks than me.
--- End quote ---

We're talking about features that don't exist. So both our ideas are from theory, which we are judging from our experience.

It seems clear to me that if the edit bar existed (including the ability to save edits) and we were considering your suggestion, the response would be, "Why don't you just use the edit bar? You could make the changes in the same time it would take you to configure your default field value settings."


--- Quote ---Knowing nostra so far, the only question is if he likes the idea or not, regardless needed effort.
--- End quote ---

It's not just a question of programming effort. It's probably safe to say what you are proposing would be useful to you. But it probably wouldn't be of much use to most other users. By tailoring a feature that is going to be useful to all so it can be applied to the widest possible number of situations—including yours—makes for software that is easier to understand, use and maintain. I'm sure this has a strong bearing on whether nostra "likes" an idea or not.

rick.ca:
The purpose of this forum is to discuss the ideas raised, in the interests of determining the best design of its implementation—in the context of the application as a whole and all of its users. The objective is to refine the idea or identify a better one, not change minds. It's not necessary to justify the reason why an idea is suggested or why anyone may want to discuss it.

I think nostra shows good judgment in deciding when and how something gets implemented. Thankfully, a suggester's insistence doesn't seem to sway him much. He can't do everything. There are quite a number of good ideas that have been discussed at length and with considerable enthusiasm but haven't yet been implemented. Some will never be implemented. In many of those discussions, no agreement was reached. That doesn't mean the discussions weren't worth having. Some of the most fruitful ones did not change any minds. :o

Navigation

[0] Message Index

[#] Next page

[*] Previous page