I am new to PHP, mySQL and scripting in general. I'm trying to design a WP custom post type which would be like a point on a timeline or an item on a resume. I'm having trouble designing the structure of the data in a nice, neat way. Each post or 'item' can be either dated or undated. If it's dated, it can either be an event, in which case it has one date attribute, or it can be a time span, in which case it has a start and end date. If it occurs over a span, that span may be 'ongoing', that it will end in the future and then the editor will come back and update the record to reflect that end date (e.g. the most recent position on a resume can be from a start date until the 'present'). The post can have content and other meta-information like a custom taxonomy, but I'm really concerned with boiling down these subcategories to the fewest number of meta fields in the WP postmeta table. The subcategories as I understand them are
- Undated Events (!Start !End !Present)
- Dated Events (Start !End !Present)
- Ongoing Time Span (Start !End Present)
- Completed Time Spans (Start End !Present)
Is this the best way to model these events/span/CV items?