One colleague voices strong support overall for the proposal, noting that it makes aggregate works definitions and guidance clearer.
Steve Shadle adds "Just want to be clear that a serially issued resource (diachronic) is not necessarily an aggregate work. A journal is an aggregate work. A frequently revised edition (which we typically treat as a serial) is not an aggregate work."
I support clearer language for definitions as Amanda suggested above. Specifically in Recommendation 3, the 3rd sentence under Aggregating works: "The work that is realized by an expression that is aggregated is not a part of the aggregating work." It seems clearer to repeat "aggregating expression" mentioned directly above, and also to reinforce that concept. I also think Kate's use of "distinct" could also help clarify the work nuances, which I initially had trouble parsing. Also, shouldn't this sentence also encompass both single and multiple works since a single distinct expression can embodied by an aggregate (which would be one work, right? I am tying myself in knots a bit today)? Something like "Distinct work(s) realized by an aggregating expression do not constitute part of the aggregating work itself."
Original Message:
Sent: Sep 27, 2024 09:54 AM
From: Kate James
Subject: Comments requested: RSC/TechnicalWG/2024/2
Hi Kathy,
My co-worker provided this comment, which I agree with although i realize it may be considered a larger issue than aggregates rather than feedback for this proposal. More explanation about the difference between the concept of "amalgamation" and "aggregate" (as a noun) would be useful, perhaps in Guidance>Aggregates. I realize that amalgamation refers to an expression and aggregate refers to a manifestation, but knowing that the manifestation contains expressions that can be separated (e.g. parallel text in English and Spanish) helps to understand you have an aggregate situation.
------------------------------
Kate James (she/her/hers)
OCLC · Program Coordinator- Metadata Engagement, Global Product Management
6565 Kilgour Place, Dublin, Ohio, 43017 United States
Original Message:
Sent: Sep 23, 2024 09:03 AM
From: Jessica Grzegorski
Subject: Comments requested: RSC/TechnicalWG/2024/2
After my first few read-throughs, I felt more or less comfortable with the proposed definitions for aggregate and aggregating work. However, I think Amanda's proposed revisions for these definitions help clarify the meaning of these terms in a way that makes them much easier to understand. I also agree that a diagram would be useful as part of the guidance chapter, perhaps one that is similar to the diagram illustrating the model for aggregates in the LRM.
I have a slight preference for retaining the original order of contents in the Toolkit for the Aggregates guidance chapter (i.e., "Aggregate manifestations" followed by "Aggregating expressions" followed by "Aggregating works"). This order more logically follows the flow of the WEMI model.
------------------------------
Jessica Grzegorski
Rare Materials Metadata Librarian
Northwestern University Libraries
She/Her/Hers
Original Message:
Sent: Sep 21, 2024 11:20 PM
From: Amanda Xu
Subject: Comments requested: RSC/TechnicalWG/2024/2
Hi Kathy: Thank you so much for sending the "Proposal to revise definitions of aggregate, aggregating work and Aggregates Guidance" for review. Here are my thoughts and suggested revision.
- Recommendation one: Aggregate: A manifestation that embodies multiple expressions.
- Recommendation two: Aggregating work: A work that is a plan to select and arrange expressions of one or more works and embody them
in an aggregate. - Recommendation three consists of the following aggregates guidance:
• Aggregate manifestations
o Collection aggregate
o Augmentation aggregate
o Parallel aggregate
• Aggregating works
• Aggregating expressions
• Describing an aggregate
For recommendation one, we need a definition to address the potential for an aggregate to contain a single expression while emphasizing the role of the aggregating expression in facilitating the aggregation of multiple expressions. It also needs to align with the feedback received from users regarding the clarity and practical application of the term within the RDA Toolkit framework. How about this definition?
Aggregate: A manifestation that embodies one or more expressions, including at least one aggregating expression, which serves to gather and organize these expressions.
For recommendation two, we need a definition that maintains clarity while emphasizing the role of the aggregating work in the selection and arrangement process, ensuring that it reflects the intention behind creating an aggregate. How about this definition?
Aggregating Work: A work that serves as a plan to select, organize, and present expressions from one or more works, ultimately resulting in their embodiment within an aggregate.
For recommendation three, we need to discuss each aggregate guidance separately.
The guidance for aggregate manifestations is comprehensive and well-articulated. Its three components: collection aggregate, augmentation aggregate, and parallel aggregate are also well-written and easily understood. The guidance on aggregating works can be refined for clarity and flow.
Aggregating work: A plan to select and arrange expressions from one or more works, embodying them in an aggregate. This plan may involve aggregating expressions of entire works, parts of works, or extracts.
An aggregating work is realized by a single aggregating expression. The work represented by an expression that is aggregated does not constitute part of the aggregating work itself.
Common attributes of the aggregated expressions may be recorded as representative expression attributes of the aggregating work. (See Guidance: Representative Expressions of an Aggregating Work.)
An aggregating work is distinct from another if the selection and sequence of expressions aggregated in one differ from those in another.
Th guidance for aggregating expressions is well-structured and informative. We can refine it for readability.
Aggregating Expression: An expression that realizes the plan of an aggregating work by selecting and arranging expressions embodied in an aggregate.
An aggregating expression is represented by an aggregate that also contains the aggregated expressions. However, it does not incorporate or accumulate those expressions or any of their characteristics.
Indirect relationships between an aggregating expression and one or more aggregated expressions can be recorded using the shortcut elements: Expression: aggregates and Expression: aggregated by. (See Guidance: Data Elements, RDA Relationship Data, Relationship Shortcuts.)
An aggregating expression does not have attributes related to content that can be recorded. (See Guidance: Resource Description, Describing an Expression, Describing Expressions of Aggregating Works and Aggregated Expressions.)
Guidance for describing an aggregate is informative. I agree with Kate that a diagram is helpful. In summary, I tried to clarify the definitions and aggregates guidance and make them easily understood by all.
------------------------------
Amanda Z. Xu
Team Lead, Librarian (Metadata)
National Agricultural Library
Beltsville, Maryland, USA
amanda.xu@usda.gov
Original Message:
Sent: Aug 28, 2024 03:05 PM
From: Kathryn Glennan
Subject: Comments requested: RSC/TechnicalWG/2024/2
A proposal has been submitted to RSC for the November meeting, https://www.rdatoolkit.org/sites/default/files/uploads/RSC_TechnicalWG_2024_2.pdf: Proposal to revise definitions of aggregate, aggregating work and Aggregates Guidance.
This proposal originated as a fast track suggestion and was referred to the full proposal process as an outcome of the July 2024 RSC meeting. The abstract says:
"Modifications of the definitions for aggregate and aggregating work are proposed for RDA, as well as revisions to the guidance for aggregates in RDA Toolkit, informed by observations from LIS trainers in teaching RDA contacted by the Education and Orientation Officer. The changes de-emphasize the role of the aggregating expression in both the definitions and the guidance."
If you have comments or suggestions on this proposal, please post them here before September 30. As usual there is a short turn around time and NARDAC would like a CC:DA response by October 1.
Note: I have already reported the problem with the missing designation of text to be deleted in the marked up text in Recommendation #1. You do not need to comment on that further.
Thanks!
Kathy
------------------------------
Kathy Glennan
CC:DA Chair
Director, Cataloging & Metadata Services
University of Maryland Libraries
she/her/hers
------------------------------