DB Schema: CollectionObjectProperties VS CollectionObjectAttribute

Regarding the following two tables:

collectionObjectAttribute VS collectionObjectProperty

  1. What are the intended purposes for them?
  2. Is there a norm on choosing one over the other?

Collection Object Attribute has a one-to-one relationship with Collection Object. You have a specimen and it has one set of attributes.
Collection Object Property has a many-to-one relationship with Collection Object. A specimen or lot, might have a variety of attributes.
Almost all of our collections use COA regardless of discipline. However, if you have a lot based collection, the COP could be useful to document different properties of different items in the lot.

1 Like

Would it make sense for the above definition for “Collection Object Property” be modified slightly to not use the word “attribute” so as to disambiguate it from the “Collection Object Attribute” definition?

Collection Object Property has a many-to-one relationship with Collection Object. A specimen or lot, might have a variety of properties.

Can we review if the “one-to-one” relationship is correct for CO => COA please?
I think it may be “ManyToOne to Collection Object”

In contrast, the CO => COP seems to be OneToMany to Collection Object"

Could we also try to explain it like: “One book can have many pages”, but “One page can only have one book”…?