-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #12 from lsgs/dev
Dev from CTSI
- Loading branch information
Showing
5 changed files
with
145 additions
and
58 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
# Change Log | ||
All notable changes to the Record Autonumbering module will be documented in this file. | ||
This project adheres to [Semantic Versioning](http://semver.org/). | ||
|
||
|
||
## [0.0.503] - 2021-04-20 | ||
### Added | ||
- Add Taryn Stoff's user guide to README (Kyle Chesney) | ||
|
||
|
||
## [0.0.502] - 2021-03-22 | ||
### Added | ||
- Revise module description in config.json to align with README (Philip Chase) | ||
- Update README based on Taryn Stoff's user guide (Kyle Chesney, Taryn Stoffs) | ||
- Fix DAG form-save bug (mbentz) | ||
- Fix crash of module when using "padded integer increment with prefix" caused by abstract method getRequiredDataEntryFields needing declaration (Kyle Chesney) | ||
- Ensure module is enabled before initializing to prevent REDCap core's autonumbering enabling in *every* project (Kyle Chesney) | ||
|
||
|
||
## [0.0.501] - 2020-12-09 | ||
### Added | ||
- Redirect with js (Luke) | ||
|
||
|
||
## [0.0.301] - 2019-05-23 | ||
### Added | ||
- Update our repository with luke's 0.0.3 changes, namely, record_autonumber_v0.0.3 (Luke) | ||
|
||
|
||
## [0.0.101] - 2019-04-19 | ||
### Summary | ||
- This is the first release. | ||
|
||
### Added | ||
- Remove default value for project-setup-dialog-text (Philip Chase) | ||
- Initial commit (Luke) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,39 @@ | ||
******************************************************************************** | ||
# Record Autonumber | ||
# Custom Record Auto-Numbering | ||
|
||
Luke Stevens, Murdoch Children's Research Institute https://www.mcri.edu.au | ||
This module allows users to create a custom record auto-numbering schema for their REDCap project. This works during data entry but not in public surveys or API/CSV data import. | ||
|
||
******************************************************************************** | ||
## Summary | ||
## Motivation | ||
|
||
Various configurable and extensible options for record auto-numbering. | ||
Applies to records created by a logged in user, i.e. not via a public survey or | ||
API/CSV data import. | ||
Normal REDCap behavior dictates that having auto-numbering enabled in a project makes the first record created have a record ID of 1, the second record created have an ID of 2, the third record created have a record ID of 3, and so on. If the project is using DAGs (Data Entry Groups), having auto-numbering enabled will automatically have its record name prepended with the Group ID (DAG ID) number and a dash/hyphen. For example, the first three records IDs created for DAG ID 98 will get automatically named 98-1, 98-2, and 98-3. | ||
|
||
******************************************************************************** | ||
This module introduces a range of additional options, such as having the first record ID created start at 1000 or 001 instead of 1, append all record IDs with a prefix (ABC-1, ABC-2, ABC-3, etc.), or having the DAG name appear in the record ID (UF-1, UF-2, UF-3) instead of the DAG ID (98-1, 98-2, 98-3, etc.) when utilizing DAGs in a project. | ||
|
||
## Limitations | ||
|
||
- The custom record auto-numbering system only applies to records *created* by a logged-in user, i.e. not via a public survey or API/CSV data import. | ||
|
||
- The module works best when enabled and configured *before* the first record has been created in the project, especially when using options 1, 2 or 3 listed below. | ||
|
||
- This module will *not* automatically convert existing records to the project's newly defined record ID schema; it only applies to *new* records that are created, by a logged-in user, once the module is enabled. | ||
|
||
## Project Configuration | ||
|
||
1. **Integer increment from a specified start value**: This option allows users to specify the first numerical record ID. Subsequent record IDs will increment from this project-wide (even for users in a DAG). | ||
- This is useful when you want your first record ID to start with any integer besides 1, including padding the 1 to become 001. | ||
|
||
1. **Padded integer increment with prefix**: This option allows users to specify a prefix to the project's record IDs and configure the padding length, prepending the ID with zeros to achieve the desired length. Subsequent record IDs will increment from this project-wide (even for users in a DAG). | ||
- This is useful when you want you need to create study-specific record IDs, such as ABC-001, ABC-002, ABC-003, etc. | ||
|
||
1. **Increment within DAG using part of the DAG name**: This option lets users create a DAG-specific prefix to the record IDs in the project, when DAGs are used in a project. This option gives users the ability to use 1-5 characters from the beginning or the end of the DAG as part of the record ID. | ||
- This is useful when you need to create DAG-specific record IDs, such as UFL-1, UFL-2, UW-1, UW-2, USF-1, USF-2, etc. | ||
- _Useful tip_: if you want the prefixed DAG ID to be "UFL" you can name the DAG "University of Florida UFL" and specify you want the last 3 letters of the DAG name to be used in the prefix. | ||
|
||
1. **Date/time in selected format**: This option will create a record ID based upon the date and time a record was created. | ||
- _Note_: Since dates are PHI, do not use this option if all data is supposed to be de-identified. | ||
|
||
1. **Unix timestamp (16 digits)**: This option will create a record ID based upon a Unix timestamp. A Unix timestamp is the number of seconds since January 1st, 1970 (UTC). | ||
- See: <https://www.unixtimestamp.com/> for more information about Unix timestamps. | ||
|
||
1. **A project-specific custom auto-numbering schema**: The module design supports the addition of novel auto-numbering schemes via custom code. This is an advanced feature for module developers. | ||
|
||
For a more detailed explanation, see the [Custom Record Auto-numbering User Guide](https://www.ctsi.ufl.edu/wordpress/files/2021/04/Custom-Record-Auto-numbering-External-Module-User-Guide.pdf) created by Taryn Stoffs. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
0.0.503 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters