Pods with Properties settable in another Pod

Hello @jamiebcove

In your case you already have made your setup. A building would be a custom post type with relationships to amenities. Each amenity would have a list of custom fields which you van fill out.

Please also see this page: https://docs.pods.io/faqs/what-can-you-build-with-pods/
And especially watch our intro videos Grow, Plan, and Build to get started.

Cheers, Jory

Hi there,

This isn’t quite what I’m looking for, I’m afraid.

We have Buildings as a Taxonomy, and Building Amenities as another Taxonomy. The current Amenities are linked as a relationship to Buildings.

I’ve tried giving Amenities a field of ‘Opening Time’, but I can only set this value for the global Amenity (on the Edit Building Amenity page).

How do I configure this so that each Amenity can have the field Opening time as a different value for each Building it’s linked to?

You really need to watch the Plan Before you Build video. Taxonomy is for grouping and filtering, not for the end points of your data unless you’re planning on writing a bunch of custom Taxonomy archives.

Building Amenities makes sense as a Taxonomy, because it can be used to filter and group, but if you’re trying to build a booking system, the rooms have to be individual entities or you can’t reserve them.

We can give you advice on structure but as we say in the FAQ we linked: we can’t design your structure for you. You have to see what works and our recommendation is always to focus on content strategy first to help define your data structure. Design a plan and test it before going to deep to see if it’s going to be able to support your structure and what you’re trying to build.

We already have a post type for the individual Listings (job-listings), which are grouped by the Unit Taxonomy, which in turn belong to a Building.

Some of the data that the end user sees on a Listing’s page is defined at Unit level, other items are set at Building Level (since we have multiple Units in many buildings).

Eg. Fake Building has Unit 12-34 and Unit 07-11. Both of those units have three Listings (rooms) within. For the end user, viewing the Listing’s page, they see both the Building Amenities, and the Unit Features (Unit Features being another taxonomy).

Since all Units within the building have access to the same facilities, we set the Amenities at the building level.

I want to be able to extend the information stored in the Amenities, so that in another section of the site, we can display detailed data about the opening hours etc of the Building’s facilities.

From what you’re saying, this isn’t possible in Pods without a full restructuring of our entire system, which isn’t something we can do. I’ll look into other solutions.