COmanage Developers List

[Arlen Johnson <>]

I'm in the process of adding the last round of breadcrumbs to the components that crossover between co person and org identity, e.g. Name, Identifiers, Email, History Records, etc. (and some that also crossover with role, e.g. phone, address).  To get these in place as quickly as possible, I'm taking the approach of building the breadcrumb trail using "CO Person" and "Organizational Identity" as placeholder text for the Primary Name that would normally be expected in the trail.  I plan to then cut a new ticket to build in the names. 

Does this sound reasonable?

Background:
----------
The breadcrumb for a typical canvas is
Home > My Population > Egan Beegan
(aside: when we have CO landing pages, there will be a crumb for that after home, e.g. Home > Demo CO > My Population > some person)

When we descend deeper into the attributes of a co person (or org id), I sometimes have access to the person's name by way of the controller, and sometimes I don't.  For example, I have the ability to replace "CO Person" with "Egan Beegan" in the breadcrumb trail for "Add a History Record" right now:

Home > My Population > CO Person > History Records > Add

But one level above this (on the History Records index), I'd need to adjust the controller to return the name to me based on the search.  This holds true across a bunch of controllers and will take time.

So my plan is to get the crumbs fully in place then go back and insert the names, which really help make it clear what we are doing at any given moment. 

Again: this sounds reasonable?  (Or would you rather I hold off and just take the time to get the names in place?)

Arlen