ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAE
1
Use casesRequirementDescriptionSetting in AMICUS/WeCatUI
From file
HeadingAccess point of recordText fieldLinkNotespriority: UC Boulder (Laura)Duke Univ. Libraries (Jacquie)Five CollegesCornell
2
1.MARC validation /tag tablesList of all the allowed MARC tags/subfields, accessible to catalogers from UIS_BIB_MARC_TAG_VLDTN S_AUT_MARC_TAG_VLDTNXaaaa
3
2.Mandatory tagsList of all the MARC tags mandatory, accessible to catalogers from UI and possibility to change the mandatory/nonmandatory settingFrom templateXA mandatory tag can be set from the "Rules setting" (see use case 8.)b. As long as we have access to do our own edits as in Line 2 above, for FOLIO version 1, we can be satisfied with the ability to go in and set our absolutely mandatory fields ourselves.
4
3.Repeteable tagsList of all the MARC tags repeteable, accessible to catalogers from UI and possibility to change the repeating/nonrepeating specificationsS_BIB_MARC_TAG_VLDTN S_AUT_MARC_TAG_VLDTNXb. As long as we have access to do our own edits as in Line 2 above, for FOLIO version 1, we can be satisfied with the ability to go in and set the repeatable fields ourselves.
5
4.Obsolete tagsList of all the MARC tags obsolete, accessible to catalogers from UI and possibility to change the obsolete/nonobsolete specificationsS_BIB_MARC_TAG_VLDTN S_AUT_MARC_TAG_VLDTNXb. As long as we have access to do our own edits as in Line 2 above, for FOLIO version 1, we can be satisfied with the ability to go in and set our add or reset obsolete fields ourselves.
6
5.Mandatory subfieldsList of all the MARC subfields mandatory, accessible to catalogers from UI and possibility to change the mandatory/nonmandatory settingFrom templateXA mandatory subfields can be set from the "Rules setting" (see use case 8.)b. As long as we have access to do our own edits as in Line 2 above, for
FOLIO version 1, we can be satisfied with the ability to go in and set
the repeatable subfields ourselves.
7
6.Repeteable subfieldsList of all the MARC subfields repeteable, accessible to catalogers from UI and possibility to change the repeating/nonrepeating specificationsS_BIB_MARC_TAG_VLDTN S_AUT_MARC_TAG_VLDTNXb. As long as we have access to do our own edits as in Line 2 above, for FOLIO version 1, we can be satisfied with the ability to go in and set mandatory subfields ourselves.
8
7.Obsolete subfieldsList of all the MARC subfields obsolete, accessible to catalogers from UI and possibility to change the obsolete/nonobsolete specificationsFrom postgres tableXb. As long as we have access to do our own edits as in Line 2 above, for FOLIO version 1, we can be satisfied with the ability to go in and set our add or reset obsolete subfields ourselves.
9
Indicators 1 and 2List of valid values for each indicatorb
10
8.Setting of rules for the check/validation of bibliographic recordList of pre-configured rules, to check and validate the record. The user can active/deactive some of these rules. See the related document in column "Link"From codeXhttps://docs.google.com/spreadsheets/d/1E8ANlH-wccJ4unCtV3y3RTomGc29wa2T-scJlWISnHU/edit#gid=1479847776ba to b. We need some on Day 1, a very few. We can add as needed, especially locally.
11
9.Setting of local tagsPossibility to add local tags for 'our legacy data', outside of current MARC21From postgres tableXXFrom Duke: Traditionally, all fields and subfields that contain the digit 9 are considered to be Local Fields. They are widely used across libraries, and documented by OCLC here:
https://www.oclc.org/bibformats/en/9xx.html
As such, I am uneasy defining these data as "legacy" since there may be no intent to remove them or update them to any other standard. Sarah at Cornell: I agree. Unfortunately, we will not be using local MARC only on legacy data, and the local MARC we use will not only be in the 9XX fields.		baa
12
10.Setting of local subfieldsPossibility to add local subfields for 'our legacy data', outside of current MARC21From postgres tableXXaa. I understand the access to local tags in Line 11 above, to include all subfields and indicators.
13
11.Adding of new Marc21 updates for tagsFrom postgres tableQuestion: Does each institution have to enter MARC21 updates? If the updates are entered centrally, how are our local tags protected?bc (for Day 1): we can add these manually, as long as we have access
14
11.1Possibility to add new tags at heading levelFrom postgres tableXX
15
11.2Possibility to add new tags at access point levelFrom postgres tableXX
16
11.3Possibility to add new tags as text fieldFrom postgres tableXX
17
12.Adding of new Marc21 updates for subfieldsFrom postgres tableb
18
12.1Possibility to add new subfield at heading levelFrom postgres tableXX
19
12.2Possibility to add new subfield at access point levelFrom postgres tableXX
20
12.3Possibility to add new subfield as text fieldFrom postgres tableXX
21
12.4Indicators
22
13. Possibility to have a linking out from MARCcat to MARC21Possibility to have a linking out from MARCcat to MARC21Xcc. With regret
23
14.Possibility to have a quickly-help tags and subfieldsPossibility to have a quick-help tags and subfield list. This list should be pulled out from text defined in local tablesOLISUITE.T_BIB_NTE_TYPE,
OLISUITE.T_BIB_HDR,
OLISUITE.T_CLSTN_TYPE,
OLISUITE.T_CNTL_NBR_TYPE,
OLISUITE.T_NME_HDG_TYPE,
OLISUITE.T_TTL_FNCTN,
OLISUITE.T_SBJCT_HDG_TYPE,
OLISUITE.T_RLTSP_TYPE		Xcb? or c, if we run out of time. For non-ctaloging staff, the quick-help is more important.
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100