LimeSurvey Manual - User contributions [en]

Email bounce tracking system

2011-11-08T15:15:45Z

Lovepade:

__TOC__

=Introduction=

The mail bounce tracking system (available in v1.91 or later) is capable of tracking down and marking the e-mails that were not delivered to the recipients (participants). The system relies on the "mail delivery notification failure report" and therefore need the administrator's e-mail address using which the e-mails were sent or a special account used only for tracking the bounces . Along with the address of the account, the credentials of the account are also required, with the connection details.

=Requirements=

the php5-imap module must be installed on your server. You can check if this is the case, by looking at the show phpinfo button, found on the global settings page:

http://i.imgur.com/ErDep.png

Then look for an imap section, like this. If an imap section is shown, you are good to go:

http://i.imgur.com/GhbRG.png

If you don't have php5-imap installed, and you have root acces to the server, your can install as per your distributions normal procedures. For e.g. Debian see this: http://www.electrictoolbox.com/install-php-imap-debian/ . Just remebmer to restart apache gracefulle: /usr/sbin/apache2ctl graceful

=How it works=

The basic idea behind the development of the system was to reduce the manual work and reducing human error’s in the way.

The basic working of this system is that when sending the mail, the mail bounce tracking system automatically adds an survey-id and token-id to the mail’s header without administrator notice.

[[File:Header.png]]

These headers ,also known as custom headers, are added to each invitation email that LimeSurvey sends to the participants.

When the mail is bounced back, the original header along with the Delievery notification header is received. The system then checks for new mail’s and parses the mail’s that have these custom header’s and mark the wrong E-Mail id in the red font color in the token’s table.

=Setting up the system=

The system is capable of working at the global level or survey level, thus the settings can be saved accordingly. The global settings can be saved under Global Settings -> Bounce Settings.

[[File:GlobalSettings.png]]

The local settings can be entered under the token management of that particular survey.

[[File:LocalSettings.png]]

[[File:LocalSettings2.png]]

As you can see in the screenshot above the setting to be used in that particular survey is to be selected. Avilable options are
* No settings to be used
* Use Local Settings
* Use Global Settings

[[File:SettingsUsed.png]]

Once the settings have been set the system only needs to be activated using the token management panel of the survey under the display tokens.

[[File:Running.png]]

Once executed the result of the scan will be shown after the refresh of the page, and of all the entries whose invitation are bounced their e-mail address are marked in red font. Also; "Email status" is chanced from "OK" to "bounced".

[[File:table.png]]

Email bounce tracking system

2011-11-08T15:13:04Z

Lovepade:

Label sets

2011-06-22T14:05:58Z

Lovepade:

__TOC__

=General=

<div class="simplebox">The function and usage of label sets have change radically with version 1.90. This page refers to v 1.90 or newer versions.</div>

Label sets are basically list templates where each list has a set of codes with labels and can be used in most question types either as answers or as subquestions. Contrary to earlier versions of LimeSurvey label sets are merely copied to the particular question as subquestion or answers. So if you change a label set after you 'used' it the changes are not propagated to the questions where a label set has been used as a template.

This new usage of label sets gives much more flexibility for future development and makes the structure of a question more logical.

<div class="simplebox">'''Hint:''' A label set must be at least contain the same base language as the survey, else you will not be able to use it for any question of your survey.</div>

An example of label set is as follows. If one wants to define a custom 7-point scale, a label set provides this function. In this example, a very simple custom label set with the code/label pairs is shown. Note that the label is what appears in the actual questions.

{|
|'''Code'''||'''Label'''
|-
|1||Not useful at all
|-
|2||2
|-
|3||3
|-
|4||Somewhat useful
|-
|5||5
|-
|6||6
|-
|7||Very useful
|}

Another graphical example:

Graphic (3 different smileys) instead of label text:

[[File:3xSmiley-Question.gif]]

=How to...=

Click on the [[File:labels.png]] "Edit/Add Label Sets"-Icon in the Administration-Menu to edit, create, delete, import or export label sets used in the 'flexible' labels questions.

==...add a new label set==
*'''Set Name:''' Each new label set has to be given a name.
*'''Languages:''' Every label set must be specified for the language it's used for. You can choose as many languages from the menu as you want.

==...import a label set==
*Create a new label set. In the screen where you can enter the label set details you will find a tab to import an existing label set. Choose a previous exported label set (either a .csv (outdated format) or .lsl file) and click on the "Import label set"-button to import. Alternative: Import a whole survey - in this case the label sets are imported with the questions. Duplicate label sets are ignored.

==...edit, delete, or export a label set==

Choose an already existing label Set in the drop-down-Box in the label set administration bar to edit, delete or export a label set.
*'''Edit label set:''' Here it´s possible to rename the Label Set and add/remove languages for this Label Set.
**To edit a label set outside of LimeSurvey (for instance, using a text editor or Excel), see this tutorial: [[Editing label sets using Microsoft Excel]].
*'''Delete label set:''' After a pop-up, you can delete the selected Label Set.
*'''Export label set:''' Export current Label Set to a .csv-File.
*'''Labels bar:'''

+To add a new label you have to fill in a label code, assessment value and label-text and press on the "Add new label"-Button. After this the label should be listed above. It's possible to use a graphic instead of or additionally to a label text. Just use HTML-code to include the graphic you want, e.g.:

<syntaxhighlight lang="php" enclose="div">

<img border="0" src="http://www.yourdomain.at/pics/pic.gif">

</syntaxhighlight>

If your label set has more than one language, you can choose which language you want to edit. Every label needs a code, an assessment value and a title. The code can only be changed in the base language of the Label Set. The assessment value can be ignored (set it to 0) if you do not use [[Assessments|assessments]]. The title is the text, which is displayed in the question.
*'''Del-button''': You can delete labels with the "Del"-button.
*'''Up/down-buttons''': It's possible to change the row of labels by the "Up" and "Dn"-buttons.
*'''Fix sort''': You can check the consistency and do a sort of the labels by pressing the "Fix Sort"-Button.

Labels which are in use by questions are hyperlinked to the question.

<div class="simplebox">(:idea:) '''Hint:''' The order of the labels can be modified by editing the label-set, however it is not possible to add new labels once the label-set is in use with question of an active survey.</div>

<div class="simplebox">(:idea:) '''Hint:''' Some useful label sets are available on the [http://www.limesurvey.org/en/additional-downloads/Label-Set-Templates/ limesurvey site]</div>

=Uploaded resources management=

This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor.

You can:
* Browse available files
* Export files as a ZIP archive
* Import a ZIP archive of files

Caution:
* Authorized file extensions are defined in config-defaults.php by your system administrator.
* Files for the survey are in the upload/labels/<lid> sub directory.
** Uploaded files will only be seen while browsing resources on this survey objects (labels) not in other labels or objects (groups, questions, answers).
** However do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who knows the URL to the file.
* Creation of sub directories of the ZIP archive won't work.
* You can't import a ZIP file containing sub directories.

Label sets

2011-06-22T13:51:45Z

Lovepade:

__TOC__

=General=

<div class="simplebox">The function and usage of label sets have change radically with version 1.90. This page refers to v 1.90 or newer versions.</div>

Label sets are basically list templates where each list has a set of codes with labels and can be used in most question types either as answers or as subquestions. Contrary to earlier versions of LimeSurvey label sets are merely copied to the particular question as subquestion or answers. So if you change a label set after you 'used' it the changes are not propagated to the questions where a label set has been used as a template.

This new usage of label sets gives much more flexibility for future development and makes the structure of a question more logical.

<div class="simplebox">'''Hint:''' A label set must be at least contain the same base language as the survey, else you will not be able to use it for any question of your survey.</div>

An example of label set is as follows. If one wants to define a custom 7-point scale, a label set provides this function. In this example, a very simple custom label set with the code/label pairs is shown. Note that the label is what appears in the actual questions.

{|
|'''Code'''||'''Label'''
|-
|1||Not useful at all
|-
|2||2
|-
|3||3
|-
|4||Somewhat useful
|-
|5||5
|-
|6||6
|-
|7||Very useful
|}

Another graphical example:

Graphic (3 different smileys) instead of label text:

[[File:3xSmiley-Question.gif]]

=How to...=

Click on the [[File:labels.png]] "Edit/Add Label Sets"-Icon in the Administration-Menu to edit, create, delete, import or export label sets used in the 'flexible' labels questions.

==...add a new label set==
*'''Set Name:''' Each new label set has to be given a name.
*'''Languages:''' Every label set must be specified for the language it's used for. You can choose as many languages from the menu as you want.

==...import a label set==
*Create a new label set. In the screen where you can enter the label set details you will find a tab to import an existing label set. Choose a previous exported label set (either a .csv (outdated format) or .lsl file) and click on the "Import label set"-button to import. Alternative: Import a whole survey - in this case the label sets are imported with the questions. Duplicate label sets are ignored.
**'''Note''': .lsl is a pain to work with. A description of how to create a .csv file, would be really nice.

==...edit, delete, or export a label set==

Choose an already existing label Set in the drop-down-Box in the label set administration bar to edit, delete or export a label set.
*'''Edit label set:''' Here it´s possible to rename the Label Set and add/remove languages for this Label Set.
**To edit a label set outside of LimeSurvey (for instance, using a text editor or Excel), see this tutorial: [[Editing label sets using Microsoft Excel]].
*'''Delete label set:''' After a pop-up, you can delete the selected Label Set.
*'''Export label set:''' Export current Label Set to a .csv-File.
*'''Labels bar:'''

+To add a new label you have to fill in a label code, assessment value and label-text and press on the "Add new label"-Button. After this the label should be listed above. It's possible to use a graphic instead of or additionally to a label text. Just use HTML-code to include the graphic you want, e.g.:

<syntaxhighlight lang="php" enclose="div">

<img border="0" src="http://www.yourdomain.at/pics/pic.gif">

</syntaxhighlight>

If your label set has more than one language, you can choose which language you want to edit. Every label needs a code, an assessment value and a title. The code can only be changed in the base language of the Label Set. The assessment value can be ignored (set it to 0) if you do not use [[Assessments|assessments]]. The title is the text, which is displayed in the question.
*'''Del-button''': You can delete labels with the "Del"-button.
*'''Up/down-buttons''': It's possible to change the row of labels by the "Up" and "Dn"-buttons.
*'''Fix sort''': You can check the consistency and do a sort of the labels by pressing the "Fix Sort"-Button.

Labels which are in use by questions are hyperlinked to the question.

<div class="simplebox">(:idea:) '''Hint:''' The order of the labels can be modified by editing the label-set, however it is not possible to add new labels once the label-set is in use with question of an active survey.</div>

<div class="simplebox">(:idea:) '''Hint:''' Some useful label sets are available on the [http://www.limesurvey.org/en/additional-downloads/Label-Set-Templates/ limesurvey site]</div>

=Uploaded resources management=

This tab lets you manage files (pictures, media files) that were uploaded in the HTML Editor.

You can:
* Browse available files
* Export files as a ZIP archive
* Import a ZIP archive of files

Caution:
* Authorized file extensions are defined in config-defaults.php by your system administrator.
* Files for the survey are in the upload/labels/<lid> sub directory.
** Uploaded files will only be seen while browsing resources on this survey objects (labels) not in other labels or objects (groups, questions, answers).
** However do not expect this limited visibility to ensure confidentiality of the resources as they are reachable with a simple browser to anyone who knows the URL to the file.
* Creation of sub directories of the ZIP archive won't work.
* You can't import a ZIP file containing sub directories.

Using regular expressions

2011-05-09T08:20:28Z

Lovepade:

__TOC__

(Perl) Regular Expressions must start and finish with a forward slash ("/"). You can find a good library of regular expressions at http://www.regxlib.net/. These patterns will almost all work if surrounded with the forward slash.

To test your regex you can [http://www.regxlib.net/RETester.aspx use this regex tester].

''Please add successfully tested regular expressions!''

Examples (note that these are all one line):

=Email Validation:=

<nowiki>/(\w[-._\w]*\w@\w[-._\w]*\w\.\w{2,3})/</nowiki>

The above regex will not validate email adresses with "+" - which is valid, and e.g. promoted by gmail. The below regex is slightly modified and allows "+":

<nowiki>/^(\w[-._+\w]*\w@\w[-._\w]*\w\.\w{2,3})$/</nowiki>

It is still far from perfect - but I think its better then the original (also because start-of-string and end-of-string anchors are added). Mind. This will allow e.g. abc+++defg@somemail.office.com. Ideally the regex should be modified to only allow one "+" charachter.

=Postcodes:=

==Australian Postcodes:==

<nowiki>/^[0-9]{4}/</nowiki>

==Canadian Postcodes:==

<nowiki>/^[a-zA-Z]\d{1}[a-zA-Z](\-| |)\d{1}[a-zA-Z]\d{1}$/</nowiki>

==US Postal Codes:==

<nowiki>/^[0-9]{5}([- /]?[0-9]{4})?$/</nowiki>

=Phone Numbers=

==US Phone Number:==

<nowiki>/^(?:$[2-9]\d{2}$\ ?|[2-9]\d{2}(?:\-?|\ ?))[2-9]\d{2}[- ]?\d{4}$/</nowiki>

or

<nowiki>/^[\.\- ]{0,}[0-9]{3}[\.\- ]{0,}[0-9]{3}[\.\- ]{0,}[0-9]{4}[\.\- ]{0,}$/</nowiki>

This second option will match all phone Canadian and US phone numbers that include non-digit symbols including

<nowiki> . ( ) - (space)</nowiki>

This will allow you to match phone numbers which resemble below.
*(555)555 5555
*555.555.5555
*555 555 5555
*(555)-555-5555
*555-555-5555
*555555555

==Australian Phone Number:==

The following patterns match all various Australian mobile and landline phone numbers including with "+61" country prefix eg:
*(02) 9123 6535
*03 1234-5345
*0412 345 678
*+61 2 3456 789

But not:
* 234 3450 234
*a234 534 3432
*134567
*123456789013

Brackets, white space and hypens are ignored.

<nowiki>NOTE: The 'PRECICE' versions listed here match against the first four or five didgets in a number to ensure that they are valid Australian numbers.

The 'NOT VERY PRECISE' only match against the first and second didgit so may allow invaid numbers</nowiki>

===All Australian phone numbers (mobile and landline - area code required)===

<nowiki>VERY PRECISE

/^$?(?:\+?61|0)(?:(?:2$?[ -]?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])|3\)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])|7\)?[ -]?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)|8\)?[ -]?(?:5[ -]?[1-4]|6[ -]?[0-8]|[7-9][ -]?[0-9]))(?:[ -]?[0-9]){6}|4\)?[ -]?(?:(?:[01][ -]?[0-9]|2[ -]?[0-57-9]|3[ -]?[1-9]|4[ -]?[7-9]|5[ -]?[018])[ -]?[0-9]|3[ -]?0[ -]?[0-5])(?:[ -]?[0-9]){5})$/

NOT VERY PRECISE

/^(?:\+?61|0)[2-478](?:[ -]?[0-9]){8}$/</nowiki>

===All Australian phone numbers (landlines only - area code required)===

<nowiki>VERY PRECISE

/^$?(?:\+?61|0)(?:2$?[ -]?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])|3\)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])|7\)?[ -]?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)|8\)?[ -]?(?:5[ -]?[1-4]|6[ -]?[0-8]|[7-9][ -]?[0-9]))(?:[ -]?[0-9]){6}$/

NOT VERY PRECISE

/^(?:\+?61|$?0)[2378]$?(?:[ -]?[0-9]){8}$/</nowiki>

===New South Wales landline phone numbers (area code optional)===

<nowiki>VERY PRECISE

/^(?:$?(?:\+?61|0)2$?[ -]?)?(?:3[ -]?[38]|[46-9][ -]?[0-9]|5[ -]?[0-35-9])(?:[ -]?[0-9]){6}$/

NOT VERY PRECISE

/^(?:$?(?:\+?61|0)2$?(?:[ -]?[0-9]){7}[0-9]$/</nowiki>

===Victorian and Tasmanian landline phone numbers (area code optional)===

<nowiki>VERY PRECISE

/^(?:$?(?:\+?61|0)3$?[ -]?)?(?:4[ -]?[0-57-9]|[57-9][ -]?[0-9]|6[ -]?[1-67])(?:[ -]?[0-9]){6}$/

NOT VERY PRECISE

/^(?:$?(?:\+?61|0)3$?(?:[ -]?[0-9]){7}[0-9]$/</nowiki>

===Queensland landline phone numbers (area code optional)===

<nowiki>VERY PRECISE

/^(?:$?(?:\+?61|0)7$?[ -]?)?(?:[2-4][ -]?[0-9]|5[ -]?[2-7]|7[ -]?6)(?:[ -]?[0-9]){6}$/

NOT VERY PRECISE

/^(?:$?(?:\+?61|0)7$?(?:[ -]?[0-9]){7}[0-9]$/</nowiki>

===South Australia, Northern Territory, Western Australia landline phone numbers (area code optional)===

<nowiki>VERY PRECISE

/^(?:$?(?:\+?61|0)8$?[ -]?)?(?:5[1-4]|6[0-8]|[7-9][0-9])$/

NOT VERY PRECISE

/^(?:$?(?:\+?61|0)8$?(?:[ -]?[0-9]){7}[0-9]$/</nowiki>

===Australian Mobile phone numbers only===

<nowiki>VERY PRECISE

/^(?:\+?61|0)4 ?(?:(?:[01] ?[0-9]|2 ?[0-57-9]|3 ?[1-9]|4 ?[7-9]|5 ?[018]) ?[0-9]|3 ?0 ?[0-5])(?: ?[0-9]){5}$/

NOT VERY PRECISE

/^(?:$?(?:\+?61|0)4$?(?:[ -]?[0-9]){7}[0-9]$/</nowiki>

=German marks (with optional plus or minus)=

<nowiki>/^[1-6]{1}[\+|\-]?$/</nowiki>

=Age Validation=

===Example: Age 20-99===

<nowiki>/([2-9][0-9])/</nowiki>

===Example: Age 18-35===

<nowiki>/(1[8-9]|2[0-9]|3[0-5])/</nowiki>

===Example: Age 19-65===

<nowiki><div class="simplebox">(1[8-9]|[2-5][0-9]|6[0-5])$</nowiki>

=Number validation=

==Numbers from 1 to 99999==

<nowiki>/^([1-9]|[1-9][0-9]|[1-9][0-9][0-9]|[1-9][0-9][0-9][0-9]|[1-9][0-9][0-9][0-9][0-9])$/</nowiki> <nowiki>/^[1-9][0-9]{0,4}$/ does the same as above but should run a little faster</nowiki>

==Numbers from 1 to 999, 1.000 to 999.999 to 999.999.999==

<nowiki>/^[1-9][0-9]{0,2}(?:\.[0-9]{3}){0,2}$/

accepts numbers from 1 to 999, 1.000 to 999.999 to 999.999.999 but

rejects numbers like 999.1.1 , 94.22.22, 999.1.22, 999.11.1, 999.1.333</nowiki>

==Number validation with optionnal decimal (for price)==

<nowiki>/^([1][0-9][0-9]|[1-9][0-9]|[0-9])[[\.)[0-9][0-9])?$/ accepts numbers from 0 to 199, with 2 decimal optionnal</nowiki> <nowiki>/^[1-9][0-9]{0,2}(?:,?[0-9]{3}){0,3}\.[0-9]{2}$/

forces two decimal points

accepts numbers from 1.00 to 999,999,999.00 with an optional comma delimiting thousands/millions

including all of the following: 1.00, 1,000.00 , 12,345.67 , 12345,02 , 123,456,468.00 , 1234566.00 , 123456789.00

but not 1,23.00 , 12,3.4 or 1234,43.04</nowiki> <nowiki>/^[1-9][0-9]{0,2}(?:,?[0-9]{3}){0,3}(?:\.[0-9]{2})?$/ same as above but the two decimal points are optional</nowiki>

==Month (1-12)==

If you want to ask for the month a person was born you can validate the input as follows:

<nowiki>/^[0]*[1-9]$|^[0]*1[0-2]$/</nowiki>

=Minimum width (set to 3 in this example)=

<nowiki>/^.{3,}$/</nowiki>

=Currency=

==US currency (dollar sign and cents optional)==

<nowiki>/^\$?\d+(\.(\d{2}]]?$/</nowiki>

==Swiss price==

A number with two decimal numbers after the decimal point of which the last one is either a 5 or a 0:

<nowiki>/^(\d+)(\.\d(05)?)?$/</nowiki>

=Validate score=

==1-10==

<nowiki>/^[1-9]{1}$|^10$/</nowiki>

==1-100==

<nowiki>/^[1-9]?[0-9]{1}$|^100$/</nowiki>

=Text validation=

currently multiple short text doesn't support minimum or maximum answers. One way around this is to use a long free text type question with a regular expression.

The following test for at least one word per line for at least 3 lines and no more than 10 lines. <nowiki>/(?:[</div>,.;:?!& \n\r]+(?: [<div class="simplebox">,.;:?!& \n\r]+)*)(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[</div>,.;:?!& \n\r]+(?: [<div class="simplebox">,.;:?!& \n\r]+)*)){2,10}/is</nowiki>If you wanted, say five words per line you could change the first and last star/asterisk to {4,} e.g. <nowiki>/(?:[</div>,.;:?!& \n\r]+(?: [<div class="simplebox">,.;:?!& \n\r]+){4,})(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[</div>,.;:?!& \n\r]+(?: [<div class="simplebox">,.;:?!& \n\r]+){4,})){2,10}/is</nowiki>If you wanted one or more words per line on between 1 and 5 lines, you can change the content of the last curley braces to {0,4} (note you use 0 because you're already matching the first line. <nowiki>/(?:[</div>,.;:?!& \n\r]+(?: [<div class="simplebox">,.;:?!& \n\r]+)*)(?:[,.;:?!& \n\r]?(?:\n|\r|\n\r|\r\n)(?:[</div>,.;:?!& \n\r]+(?: [<div class="simplebox">,.;:?!& \n\r]+)*)){0,4}/is</nowiki>

==Word count==

<nowiki>The following restricts the number of words allowed to a minimum of 1 and a maximum of 200

/^[-\w]+(?:\W+[-\w]+){0,199}\W*$/</nowiki>

<nowiki>To increase the minimum change the zero part of {0,199}

To increase or decrease the maximum change the "199" part of {0,199}</nowiki>

=Time validation=

There are a number of ways of writing time formats. Some of the possible options are 12 hour or 24 hour, with seconds or without. Currently (2009/04/06) LimeSurvey (v1.80plus) doesn't have a Time queston type so instead you can use "short free text" with one of the nine validation regular expressions below:

<nowiki>The following three validation strings test for 24 hour time (in order of appearences) without seconds, with optional seconds lastly with seconds required.

/^(?:[01][0-9]|2[0-3]):[0-5][0-9]$/

/^(?:[01][0-9]|2[0-3]):[0-5][0-9](?::[0-5][0-9])?$/

/^(?:[01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]$/~/pp<span style="color:pp~The following three match 12 hour time, as above with seconds, optional seconds and with seconds required

/^(?">00:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9] (?:pm|PM))$/

/^(?:00:[0-5][0-9](?::[0-5][0-9])? (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9](?::[0-5][0-9])? (?:[ap]m|[AP]M)|12:[0-5][0-9](?::[0-5][0-9])? (?:pm|PM))$/

/^(?:00:[0-5][0-9]:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9]:[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9]:[0-5][0-9] (?:pm|PM))$/~/pp</span>pp~The following three match either 12 or 24 hour time as above with seconds, optional seconds and with seconds required

/^(?:(?:00:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9] (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9])$/

/^(?:(?:00:[0-5][0-9](?<center>[0-5][0-9])? (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9](?</center>[0-5][0-9])? (?:[ap]m|[AP]M)|12:[0-5][0-9](?<center>[0-5][0-9])? (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9](?</center>[0-5][0-9])?)$/

/^(?:(?:00:[0-5][0-9]:[0-5][0-9] (?:am|AM)|(?:0[1-9]|1[01]):[0-5][0-9]:[0-5][0-9] (?:[ap]m|[AP]M)|12:[0-5][0-9]:[0-5][0-9] (?:pm|PM))|(?:[01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9])$/</nowiki>

=US States=

To validate for one state use the following (example is Texas):
*TX uppercase only = <nowiki>/^(TX)$/</nowiki>
*tx lowercase only = <nowiki>/^(tx)$/</nowiki>
*TX upper or lowercase = <nowiki>/^([T|t][X|x])$/</nowiki>