Can someone explain this error message?

Question

On my Suggestions Report I've come across the following error:

"931 Project Box Without Project Account."

Could someone please explain this to me and tell me how to fix it?.

Comments

In the biography, where it has {{Notables}} above the categories, you need to change that to {{Notables Sticker}} and move it to below the Biography header.

Answer 1

David, Melanie provided the instructions for how to fix the error.  

To make this whole thing a little less mysterious, we have two ways to indicate that a profile is part of a project - a project box and a project sticker.  Some profiles are managed by the project and these require the project box to be displayed on the profile.  If the project is not a manager, then it is an error for the project box to be on the profile.  In these cases, you can still indicate the profile is part of the project by using the project sticker.

I hope this helps, rather than confuses you further.  If you have any questions about it, please ask here and I promise you'll get a good and fast answer.

Comments

And this is one example (of way too many) of why so many people sign on to WikiTree, make a few dozen contributions, and then throw up their hands in despair on how (unnecessarily in my view) complicated it is, never to be heard from again.

---

Stu, I can only respond to your comment with an analogy as an example.

As a recently minted engineer (read that naive and inexperienced), I was working on avionics development, specifically the display screens providing information to the pilot.  Testing the software in the lab, the small screen had so much data that the resolution was just not sufficient to display it clearly - everything looked blurry to me and was very difficult to interpret.  I told my boss, who explained how it got to be that way.  He said that when our customer (the US Navy) provided input at the design reviews, they were senior officers, no longer flying but thrilled with all the technology that offered all kinds of things they had never had when they flew.  One Captain would say "I'd love to see {this} on the display" and another said "I'd love to see {that} on the display" and when all was said and done, we had a screen so lit up that it was more like a flashlight than a data display.  The current pilots also contributed design suggestions, but of course they couldn't say much against the recommendations of their superiors.  As a result, we added a "de-clutter" button to the display and when that was pressed, certain data would no longer appear, but it didn't seem to help enough - the display was still not clear enough, especially for the instant absorption at a quick glance required to make split second decisions appropriate to the (literally supersonic) speed at which things were happening.  Unfortunately, there's no conclusion to this story - that's just the way things were.

---

I'm well aware of the syndrome. Back in the mid-80s, I had a contract to develop and present a three-day high-level course on IBM System 360/370 architecture. The audience was new technology consultants at one of the then-Big-Eight accounting/consulting firms. These people were all recent computer science grads, expertly trained in the then-brand-new techniques of object oriented programming, but knew nothing of mainframe architecture.

The question came up in almost every class: "What sane and intelligent person would have designed something so complicated and duplicative? Why, for example, do you need IMS and CICS, both of which do essentially the same thing? Why do you need all these hardware and software add-ons to perform what would seem to be basic functions?

The answer was that no one had designed it; what had started as a simple (in design, anyway) system had over the quarter century of its existence had pieces added to it. (And in spite of it all, it had at that time ~90% of the mainframe market.)

WikiTree seems to have been down the same road -- complicated, unfortunately, by some unfortunate up-front database design decisions that would now be extremely difficult, perhaps impossible, to correct.