Opened 16 years ago
Closed 16 years ago
#194 closed enhancement (fixed)
Default export file names should be more unique
| Reported by: | Jari Häkkinen | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | major | Milestone: | MEV Launcher v1.3 |
| Component: | net.sf.basedb.mev | Keywords: | |
| Cc: |
Description
I am using the brilliant MeV extension. BASE creates the TDMS file nicely for me if it is doesn't exists, then MeV starts as expected when I click on the now colourful icon. So, I decided to look another bioassay set ... click on the less colourful icon to create a TDMS ... pop up ... click next ... error because the bioasay set has the same name (see attached screen dump) as the another bioassay set. There is a work around, select another file name for the current bioassay set.
My guess is that this problem will be seen by many users. I suggest that the default file name should concatenate the bioassay set id to the name (there is no bioassay set id in the analysis tree so maybe job id or something can be used instead). This would make the default name unique for most cases. Of course, the user may change the name manually to something conflicting but can we protect us against that?
Attachments (1)
Change History (5)
by , 16 years ago
| Attachment: | tdms_creation_error.png added |
|---|
follow-up: 2 comment:1 by , 16 years ago
| Milestone: | MEV Launcher v1.x → MEV Launcher v1.3 |
|---|
comment:2 by , 16 years ago
Replying to nicklas:
We are already protected against that since that is why you get the error message and there is also an option if the existing file is allowed to be overwritten or not.
Semantics ... the question is whether the user understands the error message or not. In an ordinary users world he has not saved a file with that name ... not for the specific bioassayset anyway. Making the connection to another bioassayset in the experiment is non-trivial for the non-implementer of the feature.
I'd still like the plug-in to make the name more unique by concatenating the bioassayset id to the default name. Of course, this does not completely avoid the problem but I say, if you tamper with the default names you are probably aware of the possible conflicts.
This is not an issue of what is right or wrong but rather increased user experience.
comment:3 by , 16 years ago
| Status: | new → assigned |
|---|---|
| Summary: | MeV TDMS file creation problem → Default export file names should be more unique |
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
We are already protected against that since that is why you get the error message and there is also an option if the existing file is allowed to be overwritten or not.