Organization Constituents: University with Departments

Baby's first post in this group! I am doing data hygiene and looking for recommendations on how to handle university/college organization accounts. 

We have several duplicate university accounts, but several are different departments at said university (i.e. department of english, art, history, etc.). I want to have one main account for the university and then link the different departments to that account instead of merging them into one monster account.

The clearest solution I've come to is associating the two organization accounts (in relationships) and then making an association type that's something like "Department/University". What's everyone else doing? 

Parents
  • I like affiliated/associated records where they make sense.

    I did a data governence project a while ago that involved tidying the relationships between org and individual or Org & sub org.  The issue has been the maintenace part of the data hygiene.  We Used attributes to classify a lot of the folks using a 2 tiered heiarchy (eg: top = Govt, lower = Local, State, Federal).  Then I wrote a report that would filter off the attribute and show the Top org in the first column (with link to the General tab) and then the Associated account and the relationship values in the subsequent columns.  If you schedule it once a month people can run their eye across it and if any changes are needed click through to the Contituent record, edit the relationship, and the continue down the report. It's an easy way to keep up to date, check the status, and update the relationship.

  • You don't still have access to that report, do you? Gov employees are the bane of my data hygiene existence. I love finding someone whose address it the office of someone who hasn't been in office for 25 years.

  • I surely do - it's in my Custom Report SSRS library.

Reply Children
No Data