What Happens in Vegas….Ends Up on Instagram!

Springshare’s heading to ALA – Las Vegas, and we’re getting Flashy in Booth #1447! All weekend long we’re delivering 15min Flash Presentations on hot topics, new products, and amazing features.

If you’re attending a Flash presentation or just stopping by Booth #1447 to say hi, be sure to tag us in your Twitter, Facebook, and Instagram posts with #SpringyFlash and #SpringyLove. Better yet, we’re giving out “I Got Flashed” stickers for all you lucky attendees!

ALA Flash Sticker

#SpringyFlash

Our Flash Presentation Schedule is available! Sign-Up today:

And remember:

What happens in Booth #1447, Stays in Booth #1447

Follow Us @Springshare

twitter-bird-light-bgs Instagram_Icon_Large Facebook

LibAnswers v2 Beta Sites – Migration Sign-up Now Available!

Attention LibAnswers v2 Beta Sites: v1 – v2 migration sign-ups start today! To choose your migration date, sign in to your v2 Beta Site and click the big green button – “Information about Migrating to LibAnswers v2″.

miginfo

Excited? Us too! But remember – the migration date you select will effectively be the GO LIVE date for your v2 system – so choose carefully! Before migration day arrives, you’ll want to do a few things in advance:

  • Pre-Migrate your key content (using the handy new tools in your LibAnswers v2 Beta Site Migration page)
    • User Accounts
    • Public FAQs
    • LibChat Departments
  • Prep replacement Widgets & API calls, and be ready to swap them in place of your v1 Widget & APIs on migration day
  • If you use a Custom Domain (anything other than xxxx.libanswers.com) for your site, you’ll need to arrange a domain transfer with your local IT department for *the same day* as your site migration

For loads more information and tools to help with all your migration needs, head to our help guide - http://support.springshare.com/libanswers/migration (must be logged in to LibApps to view).

LibGuides v2 Default Template Update

Hey LibGuides v2 Admins – this one’s for you! We pushed out an update to our default templates (for both tabbed nav and side nav) today, which requires some work on your side. ;)

Our code update only updates the default templates – it doesn’t touch your custom templates since those are, well, custom, and we don’t want to do anything to mess with them. This means, of course, that if/when we make changes to the base (default) templates, you also need to update your custom templates with the new / modified info.

  • If you are using the default templates for your guides, you don’t need to lift a finger. This update has already applied to those guides!
  • If you are using custom templates for your guides, though, you’ll want to pay attention to the next section of this post so you know how to update your templates.

In this case, we removed the gray bar that has the page name / print icon on the public side of the system. (The {{guide_nav_info}} keyword.) Previously, removing that keyword meant that you also removed the incredibly important admin side functions, but not anymore! The admin functions will remain where they are on the admin side, but the public side will be that much cleaner. W00t! :)

Before:
Public view of a LibGuides v2 guide before the template change.

After:
2014-05-13_LG2PublicGuide-After

And so, fearless LibGuides Admins, here’s what you need to do to update your custom templates:

  1. Go to Admin > Look & Feel > Guide Pages Layout > Edit a custom template.
  2. Delete this line / keyword:
    {{guide_nav_info}}

    Do not delete the surrounding <div> tags (as previously mentioned, oops!) because that will remove the super-important menus from the admin side!

    See Screenshot

  3. Add the {{page_title}} keyword to your template. In the default template, we added it just after guide title, so that line now looks like this:
    <h1 id=”s-lg-guide-name”>{{guide_title}}: {{page_title}}</h1>

    See Screenshot

  4. Add the print icon to the footer. Look for the ul tag in the footer area. Add another li tag after the one for the guide’s URL:
    <li id=”s-lg-guide-print-url”>
    <a href=”{{guide_print_url}}”><i class=”fa fa-print” title=”Print Page”></i> Print Page</a>
    </li>

    See Screenshot

  5. Save your changes.

Repeat these steps for all custom templates in your system.

If you do not make this change, at least the step to delete the {{guide_nav_info}} keyword from your templates, you will see a message on the public side of your guides telling you that it needs to be removed:

Error message if you do not update a custom template.

You also now have another Keyword Parameter option! You can choose to display the guide title on all pages of the guide, or just the homepage.

Enjoy…and let us know if you have any questions. :)

Beautiful Website Design, Made Possible with LibGuides v2 CMS

Wexler_homeThe library team at Furman University has done some amazing work with customizing LibGuides v2 CMS templates to create a website for The Peter Wexler Digital Museum at Furman University. Even though the site isn’t finished yet, and they’re still customizing their responsive design, they agreed to share it with us. We went ahead and picked their brains to share their amazing work with our community…

Q. Can you explain the Peter Wexler Project that the Furman University Library is undertaking?

A. The “Peter Wexler Digital Museum at Furman University” is a digital collection that features the life’s work of Peter Wexler, a New York theater producer, designer, and artist. The collection will be built in CONTENTdm and use LibGuides v2 as its front end. The really cool thing about this digital collection is that Peter saved virtually every draft of every design he ever created in the last 50+ years, so that viewing those items in chronological order can offer some insight into his creative process.  Another cool thing about this project is that there are very few digital collections of theater design materials, so the theater arts community has already expressed their interest in the collection after a presentation at the annual conference of USITT earlier this year.

Q. What were you using, previously, to share & display the Wexler Project? How do you envision the LibGuides v2 role in this project? 

 But I think that the bottom line, coolest thing about LibGuides v2 is the potential for using the new template functionality to create layouts that are not only responsive but also make it easier for our content authors to create more usable LibGuides for our users.

A. We decided to use LibGuides v2 to build the front end to The Peter Wexler Digital Museum for several reasons.  First, LibGuides is currently our primary website platform so we’re very familiar with its functionality, flexibility and openness.  We’ve always been able to figure out how to do what we want to in LibGuides, no matter how “outside the box”, and once we’ve got something in LibGuides we know that we can re-use it (within LibGuides) or embed it on other platforms (using LibGuides APIs).  Second, we wanted the Peter Wexler Digital Museum front end to be responsive, and we needed to learn responsive website design, so the timing of the LibGuides v2 beta, which is built to be responsive, presented a happy confluence. [Note: LibGuides v2 utilizes Bootstrap 3.0.1] We also wanted a project to focus on to help us learn the capabilities of the new LibGuides v2 templates model.

Q. You’ve been playing with LibGuides v2 for a few months now! Which features are you most excited for and why?

A. There are so many things in LibGuides v2 that sound awesome that it’s hard to pick just a few.  It would be easy to say responsive design, enhanced content-types, the new A-Z list functionality, or single sign-on across all LibApps.  But I think that the bottom line, coolest thing about LibGuides v2 is the potential for using the new template functionality to create layouts that are not only responsive but also make it easier for our content authors to create more usable LibGuides for our users.

Q. How do you envision these features and overall flexibility and openness of v2 impacting the Furman Library? 

A. Providing a device-agnostic design is very important to us.  Like everyone else, we’re seeing increased use of mobile devices.  The university rolled out a new responsive design last summer so being able to create responsive LibGuides that better meet the needs of our users is a great enhancement.  Having more options to embed LibGuides content via APIs will help us do a better job of integrating with other university web platforms.

Q. You’re a librarian with big plans! What do you plan to do with LibGuides v2 in the future?

LibGuides has really become a core tool in our web presence.

A. Well, LibGuides has really become a core tool in our web presence.  I’m interested in finding out whether a responsive design will result in increased use of our content on small, mobile devices.  I’m also working on a bunch of Google Analytics custom event trackers that I hope will give us some insights into how our users are actually interacting with our content and how we can help them to become more successful at accomplishing their most important tasks.

 

If you’re interested in learning more about LibGuides v2, templates or loads of the other cool features, be sure to sign-up for our LibGuides v2 training sessions!

Wexler Digital Portfolio

Digital Portfolio

LibGuides 2: Content Migration is Here!

You can now request migrations of your LibGuides v1 content into your LibGuides v2 Beta sites!

(We’re not sure who’s more excited right now – you or us! ;) )

Key Information:

Before we even tell you about the awesome reports we have available to you or how to request your migration, you should know:

  • Only the person who requested your beta site can schedule your content migration.
  • Once you schedule your migration, the date cannot be changed. So please be sure to discuss timing with the appropriate folks and choose your migration date carefully.
  • Migrations are limited to 10/day through May 2014.
    Starting in June 2014 it will be increased to 50/day.
  • Migration will only include data as of the day before your scheduled migration, so make sure all necessary changes are made by the end of the day the day before your migration. Example: If your migration is scheduled for May 5th, it will include content from end of day May 4th.
  • Statistics will be migrated later. Statistics migration is the next-to-last step in taking your LibGuides v2 site live.

Okay, now that we’ve gotten that out of the way, onward to other important info!

Preparing Your LibGuides v1 Data for Migration

Link to the Migrating to LibGuides v2 guide
In order to make your migration as smooth as possible, there’s some stuff you should work on first.

  • Read through the Migrating to LibGuides v2 guide.
    (You must be logged into your v2 site to access that guide.)
  • Download the pre-migration checklists from that guide.
  • Go through the reports / checklists and get your system ready!

The guide has a lot of details about migration and what you can do to get your system ready, including those checklists we promised so you can feel the complete satisfaction of crossing things off lists. *sigh* We love that.

In addition, your LibGuides v1 system has some awesome reports to help you with the “clean up” process! Our tech team worked hard to provide you with information so you don’t have to dig for it. These reports include:

  • List of reports available on the LibGuides v2 Migration screenContent-related reports on things like accounts that have not logged in for 3/6/9/12 months, guides that haven’t been updated in 3/6/9/12 months, guides with low hit counts this year, subjects / groups with no associated guides, and more!
  • A way to designate which links in your v1 system should migrate into your v2 system as Database Assets, which will automatically populate your Assets > A-Z Database List area.
  • A way to ensure all database links are mapped to the links you designated, speeding up migration time and cleaning up your system, all in one step!
  • A report of boxes that will not migrate into v2, because they either do not fit into the design of the new system or they’re being replaced with v2 options. This report helps you with planning how you want to integrate that content into your v2 guides post-migration.

Pointing out the LibGuides v2 Beta Request button on the Dashbaord of LibGuides v1Those reports can be accessed by admin-level users:

  1. Log into your LibGuides v1 system.
  2. Click the LibGuides v2 Beta Request button.
  3. Check out the reports in Section III.
  4. Of course, remember to read the guide and download checklists before heading into that area.

Requesting Your Content Migration

Okay, okay, we know it took a while to get here, but we promise all of the clean up stuff is worth it.

You can wait to schedule your migration until you’ve done your clean up, or you can schedule it now and use that looming deadline as motivation to get the clean up done…whichever works for you. ;)

Migration dates are currently available through May 2014. More will be added shortly.

Migration scheduling is first come, first served. As dates fill up (remember: 10/day through May 2014), those dates will not be available for selection in the scheduling area.

  1. Content migration screen with date selection area highlighted.Log into your LibGuides v1 system and click the LibGuides v2 Beta Request button on your Dashboard.
    • All admin-level users have access to this page to see reports / where in the migration process you are.
    • Only the person who requested the LibGuides v2 beta site will be able to set up your site’s migration date.
  2. In Step IV: Schedule Your Data Migration:
    • Read the information there.
    • Select a date and click Schedule It!
    • If your preferred date is not available, that means our dance card is full for that day. Please select another date.

That’s it! When the day comes, we’ll take care of migrating all of your content from your v1 system into your v2 system.

Check in your LibGuides v2 beta site the day after your migration and you’ll see all of your LibGuides v1 content! At that point, you’ll want to start in on post-migration clean up.

We’ll have more info on that in our Migrating to LibGuides v2 guide, along with information on going live…

LibGuides v2 A-Z Database Management Tool Updates

We’ve heard tons of great feedback from librarians who’ve checked out LibGuides v2 – and as always, thanks so much for getting in touch and letting us know what you think! One feature in particular generated more kudos and “Oh wow, that’s awesome!”s than the rest – we’ve heard your overwhelming enthusiasm for the new LibGuides A-Z Database Management tool loud and clear!

Your enthusiasm was, frankly, contagious. It inspired us to improve the A-Z Database Management tool even further, and we can’t wait to show you what we’ve cooked up! We’ve redesigned the A-Z Databases page and added two major classification facets – Databases by Type (full-text, abstracts, e-books, etc.) and Databases by Vendor. These features are available to everyone on the LibGuides v2 platform.

Redesigned A-Z Databases Page

Check out the live preview: http://springylib.libguides.com/az.php

azdatabases

We’ve redesigned the public A-Z Databases display list – the new layout is more intuitive and easier to navigate. We were particularly keen to reorganize the list filters, to make some room for some brand new options:

AZ Database Filters

Holy cannoli, that’s right – we’ve heard a lot of love out there for the new subject based classifications for databases & electronic resources, so we thought, why not take it a step further and offer even more finely grained classifications and filters? A scan of existing A-Z database guides confirmed that many folks already use classifications for “Type” of database/resource and “Vendor/Provider” of the database. These classification options are now a standard part of the “Databases” asset type in LibGuides v2 – huzzah!

Best of all, these filters work together. Let’s say a patron needs full text sociology articles – just select Subject: sociology and Database Type: Full Text, and bang – a targeted list of resources appears!

Databases by Type

We’ve seen how large an A-Z list of databases can grow, and how critical it is to offer patrons easy tools for targeted browsing. When we saw how many libraries were already building lists of resources by “type” (ie full text, abstracts, dissertations, e-books, etc), we knew we had to make it happen. Here’s how it works:

  • Admins: Head to Assets -> A-Z Databases List
  • Select Manage Database Types -> Add Database Type.
  • Add your desired types: Abstracts | Articles | Citations | E-Books | Full Text | Images | Newspapers | etc.
  • Head back to Assets -> A-Z Databases List; select Add or Edit Database
  • In the Database Types field, add as many types as you want

Databases by Vendor

Our scan also showed that many of you further sort your A-Z list of resources by database Vendor/Provider (ie ProQuest, Gale, EBSCO, etc.), so we’ve added support for this option too! Here’s how it works:

  • Admins: Head to Assets -> A-Z Databases List
  • Select Manage Database Vendors -> Add Database Vendor
  • Add your desired vendors: EBSCO | Factiva | Gale | ISI | JSTOR | Ovid | ProQuest | etc.
  • Head back to Assets -> A-Z Databases List; select Add or Edit Database
  • In the Database Types field, select a vendor

And here’s the best part: all of the new Database filter options, including Subject, Database Type, and Database Vendor, will also be supported in the new widget and API tools. In other words, not only can your users filter your overall A-Z list by these categories, but you’ll also be able to build targeted, automatically updating lists of resources based on these parameters, and embed those lists of links anywhere.

Together with the rest of the new A-Z functionality, including the ability to highlight Best Bets for each subject, and the ability to assign permalinks/friendly URL to databases, the A-Z functionality in LibGuides gives you everything you need to effectively manage your A-Z databases list. We’re confident your patrons will love the new A-Z page as well!

LibGuides v2: Content Migration FAQ

Are you ready for it? We know you are. ;)

Well, we’re nearly there! We know you have tons of questions, so we’re here to answer the ones we’re getting most often…

When will I be able to migrate my LibGuides v1 content into my LibGuides v2 system?

We’re working on the scripts and will then test them; we’ll start migrating systems after we’ve run through testing and verify the scripts are working properly. Based on our current timeline, we’re planning to start migrating systems toward the end of April.

How will I request my content migration?

There will be a button in your LibGuides v2 Beta system, similar to the one in your LibGuides v1 system for requesting the beta site.

We are also working on a scheduling system where admins can schedule their migration to run within a 24 hour period of their choice.

How long will migration take?

Once we start running the scripts, it should only take a few hours. Actual run time depends on how much content is in your LibGuides v1 system.

What will / will not transfer from LibGuides v1 to LibGuides v2?

There are more FAQs below this table regarding details for accounts and guide content, so keep reading after you look over the table!

Will be Migrated Will Not be Migrated
All User Accounts System / Group Banner Images
All Guides / Guide Content System / Group Custom HEAD Code
Statistics System / Group Custom Header Code
Images in the Image Manager System / Group Custom Footer Code
Subjects Printer Friendly Custom HEAD Code
Tags Printer Friendly Custom Header Code
Friendly URLs Printer Friendly Custom Footer Code
Groups (LibGuides CMS Only) Tab / Box Color Choices
Resource Icons Custom Analytics Code
Access Rules (LibGuides CMS Only) System / Group Homepage Options
Language Options Admin Alert Box Content
E-Reserves

If you see something missing from this list, it’s because we’re still working out details for it. :)

Will the migration overwrite any of the content I’ve already added to my LibGuides v2 Beta site?

Nope, it’ll just add new content. Anything you added before the migration will remain. :)

What if I already created accounts in my LibGuides v2 Beta system? And what account info gets migrated?

No worries! If the user’s account already exists in your Beta site, the migration will simply match up the account IDs between v1 and v2 systems so guides, etc., continue to be associated with the right account as they’re brought in.

Of course, this assumes a 1:1 match! If your v2 username is different from the one in your v1 system, it will not match and a second account will be created. So, as long as you use the same email address for your username in both sites, you’ll be all set!

As for what gets migrated: name, password, user level, profile information except: office hours, badges, custom boxes.

User Levels: LibGuides v1 Librarian and Regular account levels = LibGuides v2 Regular account level.

Password: You will use your LibGuides v1 password the first time, then will be asked to reset your password to meet the new password requirements in LibGuides v2.

Will guide content from v1 be added as the same content “type” in v2?

Yes! If you have a Links & Lists or Simple Web Links box in v1, that will be added as a General box with Link content items in v2. The same is true for books, documents & files, media / widgets, etc.

Rich text content will be added as the rich text content type in a General box as well. What will not happen is automatic translation of links within rich text areas into Link content items (a.k.a. Link Assets). You will need to make that change manually after migration is complete if you would rather change those lists of a tags into lists of Link content items / assets.

Admin level users will be able to designate which links in their v1 system should be imported into their v2 systems as Database content items.

If you have created tabbed boxes or boxes of rotating images using code from our FAQs or other code you created, those will not transfer into the system using the new Tabbed Box or Gallery Box types. That will be a manual change you’ll need to make after migration is complete.

Content will be copied in box for box. Any combining of content into one larger box will need to be done manually after migration is complete.

Will there be a guide / checklist for migration information?

Yes! We’re currently working on a whole guide all about migration: how it’s going to work and things you should do before (get your content ready to move!) / after migration (get your content ready for going live!). It’ll also include a downloadable checklist of items, so you can revel in the satisfaction of crossing things off the list. (We love that… ;) )

 

LibGuides 2 Beta Code Update Yesterday

Hey everyone – hope you’re all enjoying your LibGuides v2 beta sites! :)

We released new code into LibGuides 2 Beta sites yesterday & there are a couple of things that y’all should know as you’re using your systems today:

Rich Text Editor Update

The first one affects everyone: we released some code updates for the Rich Text Editor, including adding in those missing buttons folks have been looking for (including us) – font size, color, etc.

If you find you cannot edit rich text areas today, please clear your browser’s cache and try again. That should do the trick!

Publishing Workflow Update

Publishing Workflow - Selecting Reviewers

The second item affects LibGuides CMS 2 Beta sites only: If you had already enabled Publishing Workflow in your system, you may find that the Publish option is gone from your Status Menu options when editing a guide. That’s because we updated the way this function works! :)

Admins are no longer automatically designated as reviewers. In fact, no one is automatically a reviewer. Now you get to choose who your reviewers are right from the Publishing Workflow setup screen! Just go to Content > Publishing Workflow, enable the function (if it’s not already enabled), then select who you want to designate as reviewers in the box on the right.

Only Admin and Regular level users will appear in the selection list. Also, selected Regular level users will automatically be given rights to edit all guides in the system, since they’ll need that user permission in order to be a Reviewer. ;)

So, if you find you suddenly can’t publish guides, check your Publishing Workflow settings. If it’s enabled, select some Reviewers and you should be all set!

Request a LibAnswers v2 Beta Site!

We’re happy to announce that LibAnswers site admins can now request a LibAnswers v2 beta site via your LibAnswers v1 Admin dashboard!

LA2 Beta Site Request Button Image

Inspired by the same ideas that made LibGuides v2 possible, we’ve redesigned LibAnswers from the ground up – and we’re confident that the new version will set new standards in virtual reference management. We’ll give you the quick breakdown of all the new features below, but trust us – the new system really has to be seen to be believed!

A few quick notes about the beta site request process:

  • Your beta site will be a “blank slate” (meaning no content in it) so you can get familiar with the system and start planning your content transition.
  • Your previous site customizations will not translate to the new site framework. You’ll need to start fresh (and thanks to the new template and customization options, this will be a whole lot easier!)
  • Beta sites are outfitted with temporary communication channels (email, chat, etc.) to use for getting familiar with your site (so your live site remains your live site)
  • Once you click Submit Beta Request, we’ll do our best to install your beta site within 30 days of the original request.

But enough with the small talk – on to the v2 features!

Queues to the Rescue!

Queues are here, and they’re on a mission – to fight the forces of information overload. Queues give your site a big dose of efficiency – they’ll help you funnel questions to the right departments and people, and reduce the signal-to-noise ratio for your staff.

  • Channel Tickets to the right queues with the route that’s right for you:
    • Communication streams – Use a dedicated email address, unique question forms, an answer to a question on a shared question form, SMS numbers, twitter account, etc.
    • Self-selection – Your question forms can direct tickets to the right queue, based on intel your patrons provide.
    • Custom Forms – Create unique forms and collect customized information for different queues
  • User Permissions – Create the right level of access to the abilities and features of each queue. Assign each staff member access, per queue, to:
    • Claim & Answer Tickets
    • Publish Public FAQs
    • Admin Settings (just for that queue)
  • Targeted Notifications – Decide who to notify when new tickets arrive in each queue.

Each LibAnswers platform comes equipped with one queue. Optionally, you can add any number of additional queues – contact us at sales@springhare.com for pricing (hint – it’s only a nominal cost to add queues for departments within an individual library, and very affordable to add queues for different libraries within a single campus).

Plus, LibAnswers v2 has a lot more in store:

Streamlined Content Organization

  • Group public FAQs - Your public FAQs can be “Grouped” into searchable sub-sets of the overall FAQ. Add as many groups as you need – each gets its own:
    • Custom Layout – Our new template options make customizing layouts super easy!
    • Look and Feel – Each group gets its own homepage, topics, banner, custom code, etc.
    • Visibility Setting – Groups can be public (available to anyone) or internal (requires a site login to view).
  • Questions Restructured – we overhauled the way we treat questions in LibAnswers:
    • Questions (aka Tickets) that patrons ask are “private” no matter how they come in.
    • Ticket answers can become the base for public FAQs
  • Statistics Restructured – Those question changes have exciting implications for statistics:
    • All Ticket stats are stored together – Date & time stats, turnaround time, question method, etc.
    • All public FAQ stats are stored together too – Public FAQ views, up/down votes, views by topic, etc.

Simplified and Enhanced Librarian Views

  • Enhanced Question Collaboration – New question statuses and an improved answer page layout make it easier to collaborate on answers
  • Revised Dashboard – It’s easier to scan for the info you need, and you’ll love the new Quick Look feature.
  • All New APIs – grab any data from your LibAnswers site and display it anywhere using our new RESTful, JSON-based APIs.

Improved Look and Feel Options

  • New Look and Feel – Responsive Design that’s beautiful from the get go – thanks to Bootstrap 3, there are no longer separate “mobile” versus “desktop” views of your FAQ. Your site adjusts to render beautifully on any device!
  • Simplified Site Customization – Customize your LibAnswers pages with our brand new templating engine – we’ve made it super simple to display your pages exactly as you’d like to see them!

Plus a bevy of frequently requested features:

  • Improved cc options – now it’s easy to cc additional librarians and patrons on answers
  • User “Away” Setting – What, they let you take vacation?! Set your status to “away” to prevent questions from being assigned to you while you’re enjoying that hard-earned break.
  • Publish and unpublish public FAQs – Set your FAQs to automatically expire / publish themselves – just pick the dates, and your FAQs will become published and unpublished all by themselves!
  • Add a stat to Analytics at any time (instead of only the first time a question is answered / replied to)

 

New in LibAnalytics: Analytics Engine Overhaul

Our new analytics engine will turbo-charge your data analysis, making it possible to analyze exponentially larger datasets in LibAnalytics. What does that mean exactly? With the previous engine, sites with especially large numbers of individual records in a single dataset (in the neighborhood of 50,000 records) could experience lags and timeouts while generating reports. Fixing this issue required a major under the hood rewrite of how we store and return data. We’re happy to report that the new engine is ready for prime-time – we’ve tested it with the largest datasets we could find (more than 700,000 records!) and it performs admirably, without lags or dreaded timeouts.

Thanks to our rewritten analytics engine, we’ve also added a couple of frequently-requested reporting features:

  • Expanded Field Analysis - Run Analysis on Numeric and Text fields! To see this in action, head to a dataset and click View/Analyze Data > Field Analysis > Analyze All (Numeric or Text) Fields.
  • Frequency Analysis – The new Field Analysis options include Frequency Analysis – quickly view how frequently each numeric and text entry occurred. Just select Analyze All -> Numeric / Text fields.
  • Expanded Cross-tab Reports - We’ve added Numeric and Text fields to cross-tab analysis! Head to a dataset that contains free text and/or numeric fields and click View/analyze Data > Cross Tab Analysis.
  • “Inactive” Account Level - When a user leaves your institution, instead of reassigning all their data entries to someone else, just change their account status to Inactive. This will disable their account from logging in and recording new entries, while preserving the records they’ve created.

As always, a huge shout-out goes out to everyone who shared suggestions and feature requests – we love hearing from you!