BUG Citation Style Not Being Used or Design Flaw
In the program settings I have my citation style set to Turabian. I am a Southern Baptist and this is what our own style manual is based off of. Therefore, I would expect nothing else in the library to be any other style when the citation style in program settings is one thing. But when a new bibliography is opened it always opens with the APA Style (6th Edition) as the default style when it opens. Since my program settings are set to Turabian I think the bibliography should default to Turabian when it opens. If this is not a bug, then it is a very poor design flaw. Does anyone else see this issue with different styles?
Comments
-
Matt Hamrick said:
when a new bibliography is opened it always opens with the APA Style (6th Edition) as the default style when it opens. Since my program settings are set to Turabian I think the bibliography should default to Turabian when it opens. If this is not a bug, then it is a very poor design flaw. Does anyone else see this issue with different styles?
I am not seeing this. I have my preference set to Turabian, and every resource opens with that chosen under the book's info panel.
0 -
I thought I did too until I started opening new bibliographies.alabama24 said:Matt Hamrick said:when a new bibliography is opened it always opens with the APA Style (6th Edition) as the default style when it opens. Since my program settings are set to Turabian I think the bibliography should default to Turabian when it opens. If this is not a bug, then it is a very poor design flaw. Does anyone else see this issue with different styles?
I am not seeing this. I have my preference set to Turabian, and every resource opens with that chosen under the book's info panel.
0 -
That's a bug. New Bibliography documents should default to your global setting. I'm reporting that now. Sorry for the inconvenience.
0 -
Ok, Thanks Eli and no harm but thought it was a bug.Eli Evans said:That's a bug. New Bibliography documents should default to your global setting. I'm reporting that now. Sorry for the inconvenience.
0 -
Eli reported this back in Mar but with all the updates recently I see no fix. Are you still tracking it?
0 -
Yep, still tracking it. It's on a long-ish list of non-critical bugs, waiting for its day.
If you're curious, the way we prioritize bug fixes is a pretty standard balance of the following factors:
- How critical it is, or how much it gets in the way of your ability to use the software. Crashes are the most critical.
- How many users it affects.
- How fixable it is, that is: Can it be reproduced reliably? Is it our bug or in third party libraries?
- Whether we're planning to redesign or make large improvements to this feature in the near future and should address it then. For example, the recent Information panel design update closed about 10 long-standing non-critical but annoying bugs in the Information tool as a side effect of implementing the new design.
- Does it require specialized knowledge, and is anyone who has that knowledge available to work on it right now? This is the most variable factor.
This one is very low on the critical scale. So low that we'd call it an "annoyance" — you can still use the document, it just has a wrong default, which is annoying to change. (That's not to say it's unimportant; annoyances do add up, and we don't want that.) It's also low on the number of users affected scale, because Bibliography is not one of our most-used document types. It is very fixable, so it has that going for it. We are planning to make some improvements to the Bibliography document in the near(ish) future, and I expect this case will be caught up in that net.
Hope that helps.
0 -
Thanks Eli, I will use my fishermen patience and just wait. We did that so much in the military. You are correct it is an annoyance and I do use it extensively and more so when my studies start back up. But it's an easy change to change it when I need to.
0 -
It's been two years, and I get this is low priority, but at some point can we please get it fixed?
0 -
Matt Hamrick said:
It's been two years, and I get this is low priority, but at some point can we please get it fixed?
The fix for this will be available during the 7.7 beta cycle.
Andrew Batishko | Logos software developer
0 -
Thank you very much Andrew.
0 -
0
-
Thank you very much, this is fixed now.
0