Work is nearing completion on the next update to our MIDAS web based room booking and resource scheduling software, anticipated to be released next month.
In our previous blog post, we introduced the new setup/breakdown time features in v4.23. In this post, we’re highlighting one of the improvements we’re making in this next update to bulk modifying/deleting “similar” bookings.
The “modify similar bookings” feature allows you to select an existing booking, and then quickly locate other similar bookings for bulk modification. The “delete similar bookings” feature allows you to select an existing booking and then quickly locate other similar bookings for bulk deletion.
These features allow you to narrow down the search for “similar” bookings to those which fall within a certain date range, and/or which take place in a particular room/venue, and/or which are of a certain type.
Following customer feedback, we’re improving these options in v4.23. They’ll now also include the ability to restrict booking results to those which take place on particular days of the week.
So now, if you want to modify all similar bookings over a date range, but only include those bookings which fall on say a Tuesday, you can!
Previously, you could still do this, but you’d have to list all relevant bookings in the date range, and then painstakingly mark each of those which fell on the specific day(s) you were interested in. In MIDAS v4.23 we’re making this process far less laborious!
We’re excited about these new features and we’re sure they’ll be of great benefit to our customers! Remember, we love feedback and feature requests from our customers, so do vote and let us know what you’d like to see in future updates to our software.
Work is nearly complete on the next update to our MIDAS web based room booking and resource scheduling software, which is anticipated to be released next month.
In advance of this, we wanted to share some of the exciting new and improved features in this forthcoming release…
A commonly requested feature we’re asked for is the ability to add setup and breakdown times to bookings.
As MIDAS allows users to add custom booking fields, some customers add their own bespoke setup/breakdown fields to their MIDAS system to record how long is needed to setup/changeover. This can work well, however, using custom booking fields in this way didn’t alter the actual start/finish times of the bookings themselves. Consequently, they could only be used to denote periods within the confines of the actual start/finish times of bookings.
We’ve listened to customer usage cases. As a result, we are delighted to announce that MIDAS v4.23 will now include full support for specifying setup/breakdown times for bookings!
If these features are enabled, the standard Add/Modify Bookings screen will include two additional fields. By default theses are named “Setup” and “Breakdown” but the good news is that these names are customizable!. These fields allow specifying a setup period before the start, and a breakdown period at the end of each booking:
In the above screenshot, a booking is to be added from 8am – 10am. The booking has a 30 minute setup period before hand, and 15 minute breakdown period afterwards. The resulting booking would render in the booking grid as follows:
As you’ve come to expect from our software, we provide loads of control over settings. The new setup/breakdown time options are no different!
Firstly, the names “Setup” and “Breakdown” may not be the most applicable to your business or operational needs. So you can choose from a list of alternatives, for “Setup” these include; “Arrival”, “Build”, “Fit up”, “Get in” “Load in”, and “Rig”. For “Breakdown” these include; “Departure”, “Derig”, “Get out”, “Load out”, “Reset”, and “Strike”. If none of those are suitable, you can even enter your own bespoke labels for these pre/post booking fields. Furthermore, you can set a default value for each field. Like other booking fields, choose whether they appear on printouts, and precisely control which users these fields are presented to:
If addition to be able to control the appearance/visibility of these new fields, we’re also giving you control over their functionality, with a host of new settings:
Choose whether the times shown on the Booking Availability screen should include setup/breakdown times, you can choose whether setup and/or breakdown times for bookings are allowed to overlap with other bookings, and also whether setup/breakdown times are allowed to overlap for resources.
What’s more, you can also control how setup/breakdown times are handled with respect to invoicing:
You can include/exclude setup/breakdown times from being invoices, or indeed appearing on your invoices.
We’re excited about these new features and we’re sure they’ll be of great benefit to our customers! Remember, we love feedback and feature requests from our customers, so do vote and let us know what you’d like to see in future updates to our software.
Things are hotting up here in Europe – and we don’t mean Brexit! A heatwave is currently engulfing parts of the continent with temperatures hitting a whopping 40°C in Paris. Across the Channel here in the UK the temperature is far more bearable, and so we’ve been busy working away on development on the next release of our leading web based room and resource scheduling system, MIDAS.
We’re excited to announce that the forthcoming v4.22 update will include the often requested feature of “custom client fields”, including the ability for self-hosted MIDAS customers to attach documents (i.e. insurance certificates, contracts, etc) to client records.
Similar to the “custom booking fields” feature first introduced way back in 2010, which allows administrators to add additional booking fields to their MIDAS system on top of the standard booking fields, the new custom client fields feature will provide similar functionality to client records in your MIDAS database.
Prior to v4.22, the standard client fields in MIDAS were fixed and allowed you to capture the following items of data for each of your clients/customers:
Client name
Organization
E-mail address (or addresses)
Postal address
Telephone number
Fax number
Mobile/Cell number
Notes
The introduction of custom client fields gives you even more flexibility! Now you’ll be able to add additional fields to capture other client information that you wish to collect, for example you could add a “Salutation” list field (Mr, Mrs, Ms, Miss, Rev, Dr, etc), or a file upload field to capture an insurance document from your clients..
The types of custom client fields that may be added are the same as those available for custom booking fields, namely:
Checkbox – A “tick box” field
File – (self-hosted editions only) Allows uploading/attaching of files and documents to client records
List – A drop-down list of pre-defined items
Number – A field that will only accept numerical input
Range – A “slider” control allowing selection of a numeric value within a defined range
Text – A single-line text field
Text Area – A multi-line text field
URL – A navigable web link to an external resource
Both custom booking and custom client fields may be managed via MIDAS Admin Options → Manage MIDAS → Fields
From this screen you’ll also be able to control which client fields (both standard and custom) should be included on printouts, in search results, and on public booking/request screens. You’ll also be able to re-order client fields as well as selectively hide them from individual users too!
We’re committed to regularly bringing exciting new and improved features to our easy-to-use room booking system, MIDAS. We also work hard behind the scenes to constantly improve the overall speed and performance of both our software and infrastructure.
In this article, we’ll take a closer look at some of the performance improvements we’ve introduced over the past year. We’ll also look at some of the performance improvements you can look forward to in the very near future!
Caching and CDN
CDN stands for “Content Delivery Network”. It is a means whereby web content – such as an image – is stored on multiple servers around the world. When the image is requested by a visitor’s web browser, rather than the image being served from a single origin server (which may reside in another country), it is instead served by the nearest/fastest server in the CDN network. The result is significantly improved loading times for content served via a CDN.
Back in May last year (2018) we introduced CDN support for static content for all our cloud-hosted MIDAS customers.
As a result, we quickly saw performance improvements and reduction in load times of customer’s hosted MIDAS systems by up to 67%! You can read more about this in this blog post.
Improved DNS
DNS stands for “Domain Name System”, and can be considered as a “phone book” for the internet. When you enter a website in your browser’s address bar, a DNS system is used to look up the corresponding server on the internet that the URL you’ve entered resolves to, allowing you to then access the site.
This week, we’ve migrated our DNS to a distributed/cloud-based system. Previously, our DNS was provided by our own web servers. So for example, if you wanted to access our blog (blog.mid.as) the DNS system would first have to make contact with mid.as to find out the location of blog.mid.as.
With our new distributed/cloud-based DNS system, DNS is now handled in a similar way to the CDN system outlined above. That is to say that when you enter a URL/sub-domain for any part of our site, the DNS is resolved on a server geographically close to you.
As a result, we’re seeing DNS lookup times for our site up to 5 times faster than previously!
The above images (from dnsperf.com) show how quickly the mid.as domain used to resolve from various locations around the world (left image) and again now (right image).
XML vs JSON
What and what?! XML stands for eXtensible Markup Language. JSON stands for JavaScript Object Notation. Both are methods for storing and transporting data, with JSON being the newer of these two methods.
As we’ve been developing MIDAS for well over a decade now, XML has been the format we’ve used for the main settings file within our software for the majority of that time. This is because JSON wasn’t really around a decade ago!. The downside of using XML – particularly when used in conjunction with Perl (the language which MIDAS is written in) – is that it tends to be a little slow and clunky.
That’s why starting with our next software update, v4.22, we’ll be dropping the main XML settings file in favor of a JSON settings file instead. In our own benchmark testing, this simple change has resulted in improved load times of ~10ms per request. This may not sound a lot, but is actually quite noticeable.
As a result of this upcoming improvement, self-hosted customers will need to ensure that the JSON Perl module is installed and available on their MIDAS system in order to be able to update to v4.22.
Instructions of how to do this may be found in our How to install Perl modules KB article. Cloud-hosted customers don’t need to worry about this, as we’ve taken care of it!