Data organization terminology: when several related data items are grouped together for storage and processed as a single unit, what is this unit called?

Introduction / Context:
Fundamental data terminology distinguishes among fields (individual attributes), records (groups of fields about one entity instance), files/tables (collections of records), and databases (collections of related files/tables). Knowing these units is critical for designing forms, queries, and storage structures correctly.

Given Data / Assumptions:

• We are grouping multiple data items together for storage.
• The grouped items pertain to a single logical entity instance (for example, one employee).
• We want the standard term used in data processing and databases.

Concept / Approach:
The correct term is record. A record comprises multiple fields (for example, id, name, department), representing a single row in a table or a unit in a file. A list is a general-purpose container without the semantics of named fields. A string is a single text field, not a collection of distinct attributes. “Title” is unrelated to data grouping semantics.

Step-by-Step Solution:

Verification / Alternative check:
In relational databases, a row is a record; in COBOL files or fixed-length storage, each physical line corresponds to a record containing several fields.

Why Other Options Are Wrong:

Common Pitfalls:
Confusing a record with a file (many records) or a field (single attribute). Always map entity instance → record; attribute → field.

Final Answer:
record