| Category | Requirement | Related Jira |
---|
1 | Schema | Schema change - create new fields for Date type, Date 1, Date 2 (confirm name) Continue to map the 260$c/264$c to the publication date field as a string Remove mapping between the publication date and publicationPeriod.start/publicationPeriod.end Create new fields for Date type, Date 1, Date 2 Create new mapping between 008/07-14 and publicationPeriod.start/publicationPeriod.end based on 008/06
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODINVSTOR-1188 |
---|
|
|
2 | Data mapping | Default MARC-Instance map: | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODDATAIMP-1047 |
---|
|
|
3 | Pub start and Pub end | Map the values from Date 1 and Date 2 to the publicationPeriod.start and PublicationPeriod.end properties See above table | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODINVSTOR-1204 |
---|
|
|
4 | Instance - third pane | Create controlled list of date types to populate dropdown field for “Date type” in Instance: No dates given; B.C. date involved Continuing resource currently published Continuing resource ceased publication Detailed date Inclusive dates of collection Range of years of bulk of collection Multiple dates Dates unknown Date of distribution/release/issue and production/recording session when different Questionable date Reprint/reissue date and original date Single known date/probable date Publication date and copyright date Continuing resource status unknown No attempt to code
*No capability to change/add new values at this time | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIIN-2849 |
---|
|
|
5 | Instance - third pane | Create new section in “Descriptive data” accordion on the Instance record with a title “Type of date/Publication status” underneath “Resource type term”, “Resource type code” and “Resource type source”. Within this new section, add a table with three columnsthree new non-repeatable, not required, fields: | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIIN-2849 |
---|
|
|
6 | Instance - third pane | Create separate text boxes for “Date 1” and “Date 2” as options for Date type. These fields are not required. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIIN-2849 |
---|
|
|
7 | Filtering/ sorting | Use publicationPeriod.start and publicationPeriod.end as sources for sorting and filtering; sort off start date | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIIN-2850 |
---|
|
|
8 | Filtering/ sorting | Add new “Date” column after “Contributors” | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIIN-1876 |
---|
|
|
9 | Date column (second pane results) | In Date column, show Dates on UI based on interpretation of Date type (see stories and above table for details) | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIIN-1876 |
---|
|
|
10 | Filtering/ sorting | Create a date filter on Inventory search Instance toggle “Date range” with “To” and “From”: Inclusive range of dates, four character year (only numeric values allowed) | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIIN-2851 |
---|
|
|
11 | | Indexing Arabic numerals | |
12 | | Keep in mind date conversion | |