Skip to content

Commit 87cb48c

Browse files
pdsen-cipdsen-ci
committed
Update requirements
1 parent 5390398 commit 87cb48c

File tree

1 file changed

+314
-0
lines changed

1 file changed

+314
-0
lines changed

‎docs/requirements/v3.6.0/REQUIREMENTS.md‎

Lines changed: 314 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,314 @@
1+
2+
Requirements Summary
3+
====================
4+
5+
# default
6+
7+
## As a user, I want to execute content validation against every nth file ([#1](https://github.com/NASA-PDS/validate/issues/1))
8+
9+
10+
This requirement is not impacted by the current version
11+
## As a user, I want validate reporting output to support DD_Rule Report rule_type ([#13](https://github.com/NASA-PDS/validate/issues/13))
12+
13+
14+
This requirement is not impacted by the current version
15+
## Verify that all name/type attribute values correspond to names denoted context products ([#15](https://github.com/NASA-PDS/validate/issues/15))
16+
17+
18+
This requirement is not impacted by the current version
19+
## As a user, I want to raise a FATAL error when a catalog file is invalid ([#16](https://github.com/NASA-PDS/validate/issues/16))
20+
21+
22+
This requirement is not impacted by the current version
23+
## As a user, I want to be automatically notified when running validate that a newer version of the software is available ([#44](https://github.com/NASA-PDS/validate/issues/44))
24+
25+
26+
This requirement is not impacted by the current version
27+
## Add new target-manifest flag for user to provide a manifest (file) of file/directory paths to validate ([#50](https://github.com/NASA-PDS/validate/issues/50))
28+
29+
30+
This requirement is not impacted by the current version
31+
## As a user, I want to be warned when there are alphanumeric characters between fields in Table_Character ([#57](https://github.com/NASA-PDS/validate/issues/57))
32+
33+
34+
This requirement is not impacted by the current version
35+
## Validate Table_Character groups and their specified lengths match the specified group_length ([#63](https://github.com/NASA-PDS/validate/issues/63))
36+
37+
38+
This requirement is not impacted by the current version
39+
## As a user, I want to validate that all context objects specified in observational products are referenced in the parent bundle/collection Reference_List ([#69](https://github.com/NASA-PDS/validate/issues/69))
40+
41+
42+
This requirement is not impacted by the current version
43+
## As a user, I want validate to check number of records/fields specified in label matches the records in the actual data table ([#149](https://github.com/NASA-PDS/validate/issues/149))
44+
45+
46+
This requirement is not impacted by the current version
47+
## As a user, I want to validate PDF files are PDF/A ([#164](https://github.com/NASA-PDS/validate/issues/164))
48+
49+
50+
This requirement is not impacted by the current version
51+
## As a user, I want to validate a bundle that uses multiple versions of the Information Model / Discipline LDDs ([#188](https://github.com/NASA-PDS/validate/issues/188))
52+
53+
54+
This requirement is not impacted by the current version
55+
## As a user, I want validate to raise a WARNING when differing versions of IM are used within a bundle ([#210](https://github.com/NASA-PDS/validate/issues/210))
56+
57+
58+
This requirement is not impacted by the current version
59+
## As a user, I want to validate all data types possible per the PDS4 Information Model ([#212](https://github.com/NASA-PDS/validate/issues/212))
60+
61+
62+
This requirement is not impacted by the current version
63+
## As a user, I want to validate content for all possible PDS4 table types ([#217](https://github.com/NASA-PDS/validate/issues/217))
64+
65+
66+
This requirement is not impacted by the current version
67+
## As a user, I want to validate content for all File_Area_* products ([#229](https://github.com/NASA-PDS/validate/issues/229))
68+
69+
70+
This requirement is not impacted by the current version
71+
## As a user, I want to validate multiple bundles at once ([#237](https://github.com/NASA-PDS/validate/issues/237))
72+
73+
74+
This requirement is not impacted by the current version
75+
## As a user, I want to verify bundle directories adhere directory naming standards per SR ([#239](https://github.com/NASA-PDS/validate/issues/239))
76+
77+
78+
This requirement is not impacted by the current version
79+
## As a developer, I want an API method enable specifying of non-registered context products ([#241](https://github.com/NASA-PDS/validate/issues/241))
80+
81+
82+
This requirement is not impacted by the current version
83+
## As a user, I want validate to throw an error when more than one primary product references the same physical file ([#245](https://github.com/NASA-PDS/validate/issues/245))
84+
85+
86+
This requirement is not impacted by the current version
87+
## As a user, I want to run validate against object storage ([#266](https://github.com/NASA-PDS/validate/issues/266))
88+
89+
90+
This requirement is not impacted by the current version
91+
## As a developer, I want to utilize exit codes to differentiate failures of the process vs. validation errors ([#275](https://github.com/NASA-PDS/validate/issues/275))
92+
93+
94+
This requirement is not impacted by the current version
95+
## As a user, I want to validate when a product and label are updated, but the label is not versioned ([#279](https://github.com/NASA-PDS/validate/issues/279))
96+
97+
98+
This requirement is not impacted by the current version
99+
## CCB-264: Make the Line Feed (LF) character an allowed record delimiter ([#292](https://github.com/NASA-PDS/validate/issues/292))
100+
101+
102+
This requirement is not impacted by the current version
103+
## As a user, I want to the raise a WARNING if the object-defined size in the label does not match the file_size value ([#303](https://github.com/NASA-PDS/validate/issues/303))
104+
105+
106+
This requirement is not impacted by the current version
107+
## As a user, I want to validate that all XML Schema collections in NASA PDS archives are secondary collections ([#307](https://github.com/NASA-PDS/validate/issues/307))
108+
109+
110+
This requirement is not impacted by the current version
111+
## As a user, I want to check that all Internal References are valid references to other PDS4 products within the current validating bundle ([#308](https://github.com/NASA-PDS/validate/issues/308))
112+
113+
114+
This requirement is not impacted by the current version
115+
## As a user, I want to validate that the label references the PDS4 common schematron file which is required by standards ([#309](https://github.com/NASA-PDS/validate/issues/309))
116+
117+
118+
This requirement is not impacted by the current version
119+
## As a user, I want to validate all internal references from one product to another exist within the archive ([#316](https://github.com/NASA-PDS/validate/issues/316))
120+
121+
122+
This requirement is not impacted by the current version
123+
## As a user I want to see the name of a table/array in errors, if one is specified ([#343](https://github.com/NASA-PDS/validate/issues/343))
124+
125+
126+
This requirement is not impacted by the current version
127+
## As a user, I want to cache already downloaded schema/schematrons on the local file system ([#352](https://github.com/NASA-PDS/validate/issues/352))
128+
129+
130+
This requirement is not impacted by the current version
131+
## As a user, I want to validate that the field_number values are sequential and match the label specification for maximum number of fields ([#359](https://github.com/NASA-PDS/validate/issues/359))
132+
133+
134+
This requirement is not impacted by the current version
135+
## As a user, I want to validate all files referenced by a Product_Document ([#367](https://github.com/NASA-PDS/validate/issues/367))
136+
137+
138+
This requirement is not impacted by the current version
139+
## Improve PDF/A validation to include more robust reporting on failures ([#388](https://github.com/NASA-PDS/validate/issues/388))
140+
141+
142+
This requirement is not impacted by the current version
143+
## As a user, I want to validate all internal references to products in the PDS archive are valid ([#415](https://github.com/NASA-PDS/validate/issues/415))
144+
145+
146+
This requirement is not impacted by the current version
147+
## As a user, I want validate to throw an error when a collection inventory contains an invalid secondary product reference ([#462](https://github.com/NASA-PDS/validate/issues/462))
148+
149+
150+
This requirement is not impacted by the current version
151+
## As a user, I want to check that are no duplicate LIDs/LIDVIDs in a File_Area_Inventory ([#476](https://github.com/NASA-PDS/validate/issues/476))
152+
153+
154+
This requirement is not impacted by the current version
155+
## As a user, I want to validate labels/bundles/collections using the LBLX file extension ([#482](https://github.com/NASA-PDS/validate/issues/482))
156+
157+
158+
This requirement is not impacted by the current version
159+
## As a user, I want to validate a bundle with collections having different label extensions ([#522](https://github.com/NASA-PDS/validate/issues/522))
160+
161+
162+
This requirement is not impacted by the current version
163+
## As a user, I want to validate there are no LBLX files referenced in a bundle when XML is the expected PDS4 label extension ([#523](https://github.com/NASA-PDS/validate/issues/523))
164+
165+
166+
This requirement is not impacted by the current version
167+
## As a user, I want to receive an error when no products are found within the validation target ([#524](https://github.com/NASA-PDS/validate/issues/524))
168+
169+
170+
This requirement is not impacted by the current version
171+
## As a user, I want to receive a warning if records in file are greater than records value specified in label ([#535](https://github.com/NASA-PDS/validate/issues/535))
172+
173+
174+
This requirement is not impacted by the current version
175+
## As a user, I want to validate the DOI referenced in the PDS4 label ([#555](https://github.com/NASA-PDS/validate/issues/555))
176+
177+
178+
This requirement is not impacted by the current version
179+
## As a user, I want to be able to use validate from a docker container ([#556](https://github.com/NASA-PDS/validate/issues/556))
180+
181+
182+
This requirement is not impacted by the current version
183+
## As a user, I want to when a context product has been deprecated ([#592](https://github.com/NASA-PDS/validate/issues/592))
184+
185+
186+
This requirement is not impacted by the current version
187+
## As a user, I want to validate all collections referenced from a bundle exist within the archive ([#595](https://github.com/NASA-PDS/validate/issues/595))
188+
189+
190+
This requirement is not impacted by the current version
191+
## As a user, I want to validate all products referenced from a collection exist within the archive ([#596](https://github.com/NASA-PDS/validate/issues/596))
192+
193+
194+
This requirement is not impacted by the current version
195+
## As a user, I want to be able to use both online and local schema/schematron files. ([#599](https://github.com/NASA-PDS/validate/issues/599))
196+
197+
198+
This requirement is not impacted by the current version
199+
## As a user, I want to validate MP4/H.264 encoded video as observational data ([#604](https://github.com/NASA-PDS/validate/issues/604))
200+
201+
202+
This requirement is not impacted by the current version
203+
## As a user, I want to validate MP4/H.264/AAC encoded video with audio as observational data ([#605](https://github.com/NASA-PDS/validate/issues/605))
204+
205+
206+
This requirement is not impacted by the current version
207+
## As a user, I want to capture registry referential integrity output as a JSON report ([#609](https://github.com/NASA-PDS/validate/issues/609))
208+
209+
210+
This requirement is not impacted by the current version
211+
## As a data engineer, I want to run the validator multi-threaded. Is that a possibility now or in the future? ([#612](https://github.com/NASA-PDS/validate/issues/612))
212+
213+
214+
This requirement is not impacted by the current version
215+
## As a user, I would like to enforce browse file extension with encoding type ([#617](https://github.com/NASA-PDS/validate/issues/617))
216+
217+
218+
This requirement is not impacted by the current version
219+
## As a user, I want to throw a WARNING when a product's schematron version does not match the schema version ([#628](https://github.com/NASA-PDS/validate/issues/628))
220+
221+
222+
This requirement is not impacted by the current version
223+
## As a user, I want to support bit patterns within Special_Constants values ([#651](https://github.com/NASA-PDS/validate/issues/651))
224+
225+
226+
This requirement is not impacted by the current version
227+
## As a user, I want the PDF error reports to be output in a user-specified directory ([#658](https://github.com/NASA-PDS/validate/issues/658))
228+
229+
230+
This requirement is not impacted by the current version
231+
## As a user, I want to validate WAV encoded audio as observational data ([#662](https://github.com/NASA-PDS/validate/issues/662))
232+
233+
234+
This requirement is not impacted by the current version
235+
## As a user, I want to validate M4A/AAC encoded audio as observational data ([#663](https://github.com/NASA-PDS/validate/issues/663))
236+
237+
238+
This requirement is not impacted by the current version
239+
## As a user, I want to receive a WARNING when table objects are out of order ([#683](https://github.com/NASA-PDS/validate/issues/683))
240+
241+
242+
This requirement is not impacted by the current version
243+
## As a user, I want to throw an error when numeric values are padded by whitespace in delimited tables ([#722](https://github.com/NASA-PDS/validate/issues/722))
244+
245+
246+
This requirement is not impacted by the current version
247+
## As a user, I want validate's referential integrity tool to read a manifest of files and check referential integrity ([#741](https://github.com/NASA-PDS/validate/issues/741))
248+
249+
250+
This requirement is not impacted by the current version
251+
## As a user, I want validate to throw an error when a file is being referenced by more than one label ([#755](https://github.com/NASA-PDS/validate/issues/755))
252+
253+
254+
This requirement is not impacted by the current version
255+
## As a user, I want validate with the registry when a file is being referenced by more than one label ([#773](https://github.com/NASA-PDS/validate/issues/773))
256+
257+
258+
This requirement is not impacted by the current version
259+
## As a user, I want to sacrifice resources for faster processing ([#774](https://github.com/NASA-PDS/validate/issues/774))
260+
261+
262+
This requirement is not impacted by the current version
263+
## As a user, I want to have the same information available in the validation report no matter which style I choose ([#797](https://github.com/NASA-PDS/validate/issues/797))
264+
265+
266+
This requirement is not impacted by the current version
267+
## As a user, I want a WARNING to be thrown when a delimited or character table value does not match the expected `field_format` ([#816](https://github.com/NASA-PDS/validate/issues/816))
268+
269+
270+
This requirement is not impacted by the current version
271+
## As a user, I want an ERROR to be thrown when a character table value does not match the expected `validation_format` ([#817](https://github.com/NASA-PDS/validate/issues/817))
272+
273+
274+
This requirement is not impacted by the current version
275+
## As a user, I want to have the parameter names used in 3.5.0 reports to be the same as they were in ≤3.4.1 ([#827](https://github.com/NASA-PDS/validate/issues/827))
276+
277+
278+
This requirement is not impacted by the current version
279+
## As a user, I want validate to allow delimited tables with whitespace-only numeric fields ([#850](https://github.com/NASA-PDS/validate/issues/850))
280+
281+
282+
This requirement is not impacted by the current version
283+
## As a user, I want to receive a WARNING message when the `Observing_System_Component.name` does not match the value in the context product ([#857](https://github.com/NASA-PDS/validate/issues/857))
284+
285+
286+
This requirement is not impacted by the current version
287+
## As a user, I want to receive a WARNING message when the `Target_Identification.name` does not match the value in the context product ([#861](https://github.com/NASA-PDS/validate/issues/861))
288+
289+
290+
This requirement is not impacted by the current version
291+
## As a user, I want to throw an WARNING when `Time_Coordinates.start_time` does not match or come before `Time_Coordinates.stop_time` ([#964](https://github.com/NASA-PDS/validate/issues/964))
292+
293+
294+
This requirement is not impacted by the current version
295+
## As a user, I want to includes aliases in context product name validation ([#970](https://github.com/NASA-PDS/validate/issues/970))
296+
297+
298+
This requirement is not impacted by the current version
299+
## As a user, I want to check that the `object_length` is valid when specified for a delimited table ([#978](https://github.com/NASA-PDS/validate/issues/978))
300+
301+
302+
This requirement is not impacted by the current version
303+
## As a user, I want to validate that there is exactly one digit to the left of the decimal point for the specifier `e` or `E` ([#992](https://github.com/NASA-PDS/validate/issues/992))
304+
305+
306+
This requirement is not impacted by the current version
307+
## As a data archivist/validator, I want to ease the sifting of error logs with two types of output reports ([#1035](https://github.com/NASA-PDS/validate/issues/1035))
308+
309+
310+
This requirement is not impacted by the current version
311+
## As a user, I want to run a windows CI smoke test on push to branch ([#1056](https://github.com/NASA-PDS/validate/issues/1056))
312+
313+
314+
This requirement is not impacted by the current version

0 commit comments

Comments
 (0)