Custom Development

Antiquity Database has been designed to be extremely flexible and so meets most business needs. However, sometimes a customer asks for something that isn't built into Antiquity. Here's how we deal with these situations.

This page is about custom development for your Antiquity database.
For website personalisation, customisation or bespoke websites, please see the Antiquity Web pages or contact us with your requirements.

We welcome your feedback and suggestions for changes and new features that will help make Antiquity even better. Some changes can be implemented at no charge and a quotation wil be provided for others. Quotations vary depending on the complexity and / or urgency of the work. Should you proceed, we will ask you to sign a work authorisation document for anything over an hour, so you will never receive an invoice that you weren't expecting.

Option 1

Repurpose an existing feature

We will see if there is a way to repurpose an existing feature in Antiquity Database that you're not currently using. This is the simplest and quickest solution and usually incurs no cost.

For example, in Antiquity you can create a list of artists / makers (A/M) along with their biographies and dates born & died. You then link stock items to their respective A/M. This makes it easy to find all the items by a specific A/M in Antiquity or on an Antiquity website.

Patrick Sandberg didn't use this feature but he did want to categorise his antique furniture into periods, e.g. Georgian, Regency, Victorian, Edwardian etc.

With absolutely no customisation whatsoever, Patrick simply repurposed the A/M feature and created a list of periods instead. Each period has a title (instead of an A/M name), a description (instead of a biography) and the years born & died have been used for the years of the respectivea period.

On Patrick's
Antiquity website, we renamed his A/M page to "Furniture Styles" (a zero cost part of our standard website personalisation) and now his customers can click on a period they are interested in, read the description and immediately see all the stock items available in that period.

Option 2

Simple Changes

You request something that is technically simple to implement, will take very little time and will likely be useful to other Antiquity Database customers too.

Such changes will usually be implemented at low cost (or maybe no cost) in both your copy of Antiquity as well as our development copy, so you benefit from it now and other Antiquity customers can benefit from it when the next update is released.

Option 3

Complexity

Medium / Complex

Urgent

No

Medium or complex customisation requests without any urgency will be added to our list and may be moved to our development schedule when there is sufficient demand from other customers. We log all customer requests that fit in with the general direction of development.

There will be no cost but there is also no guarantee if or when your request will be implemented or released.

Option 4

Complexity

Medium / Complex

Urgent

Yes

More urgent customisation requests are sponsored by the customer. We will review your request and provide a quotation. If multiple customers request the same change then the costs can be shared, if all parties agree.

Such changes will be implemented in your copy of Antiquity as well as our development copy, so you benefit from it now and other Antiquity customers can benefit from it when the next update is released.

Option 5

Anything Else

Any unique requests or ones that either don’t fit in with the general direction of Antiquity development or that would not benefit the majority of our customers can be built as a separate but integrated module. As above, we will review your request and provide a quotation.

This type of development will usually only be implemented in your copy of Antiquity but not the development version. Future updates to the Antiquity Database won’t usually impact your custom modules, but they may require some additional development work from time to time to remain compatible.