prevent_past_or_future_dates

This REDCap module adds actions tags @PREVENT-FUTUREDATE and @PREVENT-PASTDATE that can be applied to date fields - i.e., a text field with date validation applied.

https://github.com/ctsit/prevent_past_or_future_dates

Science Score: 57.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 3 DOI reference(s) in README
  • Academic publication links
    Links to: zenodo.org
  • Academic email domains
  • Institutional organization owner
    Organization ctsit has institutional domain (www.ctsi.ufl.edu)
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (6.1%) to scientific vocabulary

Keywords

redcap redcap-external-module redcap-repo
Last synced: 6 months ago · JSON representation

Repository

This REDCap module adds actions tags @PREVENT-FUTUREDATE and @PREVENT-PASTDATE that can be applied to date fields - i.e., a text field with date validation applied.

Basic Info
  • Host: GitHub
  • Owner: ctsit
  • License: other
  • Language: JavaScript
  • Default Branch: master
  • Homepage:
  • Size: 99.6 KB
Statistics
  • Stars: 1
  • Watchers: 5
  • Forks: 5
  • Open Issues: 2
  • Releases: 3
Topics
redcap redcap-external-module redcap-repo
Created about 5 years ago · Last pushed over 1 year ago
Metadata Files
Readme Changelog License Authors Zenodo

README.md

Prevent Past or Future Dates

DOI

This REDCap module adds actions tags @PREVENT-FUTUREDATE and @PREVENT-PASTDATE that can be applied to date fields - i.e., a text field with date validation applied - to disallow entry of dates in the future or past, respectively. The tags are mutually exclusive, applying both tags will not result in any date restrictions. To enforce today's date use the @TODAY action tag instead.

Prevent Future Date

Prerequisites

  • REDCap >= 14.0.2
  • PHP >= 7.4

Installation

  • Clone this repo into to <redcap-root>/modules/prevent_past_or_future_dates_v0.0.0.
  • Go to Control Center > Manage External Modules and enable Prevent Past or Future Dates.
  • For each project you want to use this module, go to the project home page, click on Manage External Modules link, and then enable Prevent Past or Future Dates for that project.

Expected Behavior

Scenarios

| | Applied Tags | Dates available in Datepicker | | ------------- | ------------- | ------------- | | Scenario 1 | @PREVENT-FUTUREDATE | past - today | | Scenario 2 | @PREVENT-PASTDATE | today - future | | Scenario 3 NOT SUPPORTED | @PREVENT-FUTUREDATE && @PREVENT-PASTDATE | N/A - supplying both tags will not apply any date restrictions use @TODAY instead |

Existing Data

The action tags will only apply to empty fields; if data already exists in a field when the form is loaded the action tag will not apply to that field. This is to prevent annoyances when revisiting forms.

Date vs Datetime field

This module handles date fields and datetime fields slightly differently: * If a datetime field fails validation and the datetimepicker is opened and loses focus, the input will be updated automatically to the closest valid date. * If a date field fails validation and the datepicker is opened and loses focus, the input will not be updated automatically. A validation alert will display and the value will need to be updated manually.

Owner

  • Name: CTS-IT
  • Login: ctsit
  • Kind: organization
  • Location: 2401 Archer Road Gainesville, FL 32608

Clinical and Translational Science Informatics and Technology, University of Florida

GitHub Events

Total
Last Year

Issues and Pull Requests

Last synced: over 1 year ago

All Time
  • Total issues: 7
  • Total pull requests: 6
  • Average time to close issues: 7 months
  • Average time to close pull requests: 5 months
  • Total issue authors: 3
  • Total pull request authors: 2
  • Average comments per issue: 1.71
  • Average comments per pull request: 1.67
  • Merged pull requests: 5
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 3
  • Pull requests: 1
  • Average time to close issues: 13 days
  • Average time to close pull requests: about 2 hours
  • Issue authors: 1
  • Pull request authors: 1
  • Average comments per issue: 1.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 1
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • pbchase (5)
  • lawrai (1)
  • tlstoffs (1)
Pull Request Authors
  • michael-bentz (6)
  • saipavan10-git (2)
Top Labels
Issue Labels
Pull Request Labels