Microsoft assumes their users are complete idiots, even when they (the users) are actively trying to convince them (Microsoft) otherwise. No matter how advanced the feature may be, they'll assume you found instructions somewhere to do something entirely unrelated and they constantly have to save you from yourself. As a result you constantly have to fight the OS for access and control to get it to do what you want.
If you're even a bit of a power user that is, of course.
But more often than not Microsoft's assumption is probably spot on.
The thing is, that excel already has half the means of what would be necessary to really fix this bug. That is a field for each cell where the original text can stay.
An excel sheet is just a bunch of XML files zipped in a specific structure. You can unpack a file and look for yourself.
Each worksheet is it's own file and each cell is subdivided into the value and the formula, that generated this value (or nothing, if there is no formula).
Excel could easily fix this issue by adding another possible cell attribute like "original" or "plain" that, when set, allows you to roll back any conversion.
But no, they go a half assed way as always and screw up even more.
Excel is never ever going to break backwards compatability. In fact, quite some "features" in Excel are just there to stay bug-for-bug compatible with existing systems.
Example: Excel stores dates internally as a float - called the serial date, you can view it by running DATEVALUE on any cell that contains a date. It is supposed to be the number of days since 1 January 1900. However, since early Excel versions had to be compatible with Lotus1-2-3, Excel had to be compatible with a bug in Lotus123: they had erroneously assumed 1900 to be a leap year. In addition, the indexing is off by one. So the actual 0 epoch of an Excel serial date is 30 December 1899 for all dates starting 1 March 1900.
Microsoft’s blog adds caveats, such as that Excel avoids the conversion by saving the data as text, which means the data may not work for calculations later. There’s also a known issue where you can’t disable the conversions when running macros.
I remember when a biologist asked us for help - Excel crashed on processing his 700MB tables. Took some time and Chatgpt to convince him to do the analysis in R. It worked out in the end and he is now recommending this solution to his colleagues, which is nice.
Excel sucks open ass. At storing data, at displaying data, at analyzing data. Scientists, of all people, should understand how to use an RDBMS and a data processing framework like R.
Thank god! You have no idea how awful this is for scientists. Need to paste some gene names down? Better hope it’s not MARCHF8 or in the Septin gene family, otherwise you have to convert columns to text then import the data. Seems like a simple fix, but many wet lab biologists are technologically challenged.
"Microsoft’s blog adds caveats, such as that Excel avoids the conversion by saving the data as text, which means the data may not work for calculations later. There’s also a known issue where you can’t disable the conversions when running macros. "
It's no good having this as part of the user options. It should be a sheet characteristic and the default should be "keep cells exactly as entered regardless of data type".
You could make a new filetype, default new versions to it, & not break compatibility. Wouldn't do anything for existing workbooks, and keep xlsx an option, but "it would break compatibility" is not a be-all end-all argument against this.
I think the point was that the format itself is odd. I am European and it's weird to me: logically it should be either from greatest to smallest, or from smallest to greatest, not a weird in-between.
In 2020, scientists decided just to rework the alphanumeric symbols they used to represent genes rather than try to deal with an Excel feature that was interpreting their names as dates and (un)helpfully reformatting them automatically.
Yesterday, a member of the Excel team posted that the company is rolling out an update on Windows and macOS to fix that.
Excel’s automatic conversions are intended to make it easier and faster to input certain types of commonly entered data — numbers and dates, for instance.
But for scientists using quick shorthand to make things legible, it could ruin published, peer-reviewed data, as a 2016 study found.
Microsoft detailed the update in a blog post this week, adding a checkbox labeled “Convert continuous letters and numbers to a date.” You can probably guess what that toggles.
The update builds on the Automatic Data Conversions settings the company added last year, which included the option for Excel to warn you when it’s about to get extra helpful and let you load your file without automatic conversion so you can ensure nothing will be screwed up by it.
The original article contains 225 words, the summary contains 184 words. Saved 18%. I'm a bot and I'm open source!
Many scientists are based out of corporations or universities who contract with Microsoft, so Excel would be the default solution for working with spreadsheets.
Also, when it comes to “office” applications, there is no real substitute for Excel. Word processing, presentations, email, notes; there are many open and closed source alternatives that will do the same if not better than MS Office applications. Excel, however, is the exception.
LibreOffice Calc, G-Sheets, Apple’s Numbers, or the myriad of competitor office solutions have never matched Excel for in-depth analyses or overall function. For just basic features, one could limp by with most alternatives, but doing real analytical work within spreadsheets requires Excel.
In college a professor gave us some homework to be done in excel, and as the nerd that I am, I asked if Livre Office was ok because I use Linux and have no access to Excel. The professor was like, well in that case everyone do the homework on R or python. My classmates were really mad at me for that.
By experience, being a scientist doesn't mean one is the smartest guy in the room. Just that one has passion and luck and luxury to pursue that passion.
Many use alternatives to excel (R, python, Matlab, libreoffice).
For others installing a software is challenging enough that they use whatever provided by IT.
The remaining don't give a sh*it, they are too busy in exploiting or in being exploited. No time to think about what is better
I've had the same copy of excel since high school, and it's done a damn fine job processing experimental date through undergrad, my PhD, and 6 years as a working researcher.
It's also the software pretty much everyone has, so you can easily share data with collaborators and other researchers. And it has a ton of functionality so you can process and analyze data easily, and create the visuals for papers very easily.
You are completely right, and the Open Science movement is catching on. The idea is to give everyone access to the (anonymised) data and use only tools that are freely accessible, even to scientists from developing countries without Microsoft licenses, so that they too can rerun your analyses and verify your results. You shouldn't be getting downvoted.
This isn't a fix. Excel wasn't meant for this.
While I do understand it's convenient as a database, unless you're doing something unimportant and small you just really should use something proper. And even now that this "problem" is gone, I am certain there are still more things that cause trouble. You can not satisfy everyone and Excel was just... not made for gene info storage.
Even if you don't want to use stuff that isn't Microsoft Office, that comes with Microsoft Access, which is a proper database management system. It's literally in the same software package, so why do people refuse to use it?
Why would you need a full blown (shitty) relational database management system to store gene info? Excel should be just fine for storing data in arbitrary tables. It shouldn't make assumptions about your data by default, and changing values that look like they're in a specific format should be opt-in, not default behavior.
It shouldn't make assumptions about your data by default, and changing values that look like they're in a specific format should be opt-in, not default behavior
But that's exactly what made the "auto" data type of Excel such a powerful tool when introduced. If you're storing text, make the datatype "text", problem solved.
Nowadays, when making stuff like Excel from scratch, you could opt for a "these look like dates, change the type from 'none' to 'date'?" but with middle management being conditioned on the data type being 'auto', that's something that's hard to change.
That is not what it was made for. It was made to do shenanigans with values like doing math on them and plotting graphs. If you merely want data storage, use a table. I agree, a database is overkill for most things, but that doesn't change the fact that Excel is the wrong tool for the job. Maybe if they added a table mode where it's basically just a frontend for a csv it'd work, but right now I'd still say it's better to use a scalpel than a hammer, even if scissors do the trick just fine.
The problem of Excel software (Microsoft Corp., Redmond, WA, USA) inadvertently converting gene symbols to dates and floating-point numbers was originally described in 2004 [1]. For example, gene symbols such as SEPT2 (Septin 2) and MARCH1 [Membrane-Associated Ring Finger (C3HC4) 1, E3 Ubiquitin Protein Ligase] are converted by default to ‘2-Sep’ and ‘1-Mar’, respectively. Furthermore, RIKEN identifiers were described to be automatically converted to floating point numbers (i.e. from accession ‘2310009E13’ to ‘2.31E+13’). Since that report, we have uncovered further instances where gene symbols were converted to dates in supplementary data of recently published papers (e.g. ‘SEPT2’ converted to ‘2006/09/02’). This suggests that gene name errors continue to be a problem in supplementary files accompanying articles.
Libre calc is one of the worst UXs I have ever had the displeasure of using. I can't imagine anyone recommending it is using it as their main work application.