August 17, 2015

What's New in Edifix 2.2

Pineapple sits in green grass

When you logged on to Edifix today, did you notice the snappy green asterisks next to the Blog link? Some of us think it looks like the top of a pineapple, as seen from above. Some of us are dreaming of a tropical summer holiday...

These little asterisks/pineapple tops will let you know that there’s a new blog post to read! In this exciting installment, you’ll learn about what’s new in our August release of Edifix 2.2.

New Styles!

We’ve updated the names of our editorial style options. This should decrease ambiguity around editorial styles that are known by many different names. We think the renamed options look better too (“APA 6th ed.” instead of “APA6” is a lot better, right?).

We’ve also added two new editorial style templates from two amazing scholarly societies to our collection:

SEG (Society of Exploration Geophysicists)

According to their Instructions to Authors:

Authors are requested to be meticulous in following instructions for references, which typically require more editing than any other section of the manuscript. In addition, accuracy and proper form are essential so that references in online Geophysics papers will link to the sources cited. Authors who do not follow guidelines for references can expect a delay in publication because the article may be returned for revision to proper style.

We hope authors are thrilled that we now support SEG’s reference style!

An example journal article and book chapter reference:

  • Anders, A. M., G. H. Roe, D. R. Hallet, N. J. Montgomery, N. J. Finnegan, and J. Putkonen, 2006, Spatial patterns of precipitation and topography in the Himalaya, in S. D. Willett, N. Hovius, M. T. Brandon, and D. M. Fisher, eds., Climate, and Landscape Evolution: The Geological Society of America, 39–53.
  • Tanaka, Y., and K. Heki, 2014, Long- and Short-Term Postseismic Gravity Changes of Megathrust Earthquakes from Satellite Gravimetry: Geophysical Research Letters, 41, no. 15, 5451–5456.

ASM Press (American Society for Microbiology)

An example journal article and book chapter reference:

  1. Caserta E, Haemig HAH, Manias DA, Tomsic J, Grundy FJ, Henkin TM, Dunny GM. 2012. In vivo and in vitro analyses of regulation of the pheromone-responsive prgQ promoter by the PrgX pheromone receptor protein. J Bacteriol 194:3386–3394. PMID:22544272
  2. Forman MS, Valsamakis A. 2011. Specimen collection, transport, and processing: virology, p 1276–1288. In Versalovic J, Carroll KC, Jorgensen JH, Funke G, Landry ML, Warnock DW (ed), Manual of clinical microbiology, 10th ed, vol 2. ASM Press, Washington, DC.

You can learn more about the ASM reference style in their Instructions to Authors.

New Exports!

Your references aren’t meant to simply sit in Edifix forever. They need to be incorporated into your Word file, your reference manager, your publishing service, or other workflow. In addition to copying and pasting your references, you can always export your references to JATS (NLM) XML, or Medline or RIS format for integration with your favorite reference manager.

In this release, we’ve added FOUR new export options, making it easier to get your corrected and structured references out of Edifix and into the world:

  • HTML: Export your references as an HTML webpage to save or copy/paste from later on.
  • Word DOC: Export your references as an HTML-formatted* Word document.
  • Medline (UTF-8): Export your references to Medline format with UTF-8 encoded special characters. If your reference manager does not support UTF-8 encoding, please continue to use the simple Medline export, which uses only US-ASCII characters.
  • RIS (UTF-8): Export your references to RIS format with UTF-8 encoded special characters. If your reference manager does not support UTF-8 encoding, please continue to use the simple RIS export, which uses only US-ASCII characters.

*Note that HTML-formatted Word documents will often open in Word's Web Page View.

New Team Members!

We are also very excited to welcome Jenny and Patrick to the Edifix Team! Our little family is growing more and more.

Have new features to request or bugs to report for our next release cycle? We're always happy to hear from you.