Gratian

Bug #663024
Comment #3

Comment 3 for bug 663024

Revision history for this message

Teffania (teffania) wrote on 2010-12-14:

For interest and comparison:
Page example from Anealan Op
http://aneala.sca.org.au/OP/person.asp?id=2
the concept of free text space for persona description is interesting

From memory one of the other kingdoms has photos and contact details, but it also lacks the database structure of Canon lore you can only rigidly look up a person in a particular way (searhc I think, no browse, no similar hits either), no browsing no getting distracted by who else got awards at that event, who was reigning, who regned before the etc....

Personally, I think photos and stuff are generally going to be more work than blessing. Ok photos might be cool, but post implementing stuff like this - always a lot of data entry work. We don't want the short termism of facebook photos, but instead a phptp intended to last 10 years. And then there is the isues of permission - we need the photographers's explicit permission to use the photo, and then it would be a very good idea to have the person in the photos permision to use that photo - a nightmare to chase up. And then there will be people who don't want to be identifiable by workmates for whom other scadians constantly pester sending in photos for. Even with the theoretical team of data entry ppl and everyone uploading their photo in the correct format, how do we prove the person is the one with the rights to approve copyright on a photo or is the person in the photo? Can of worms.

One possble useful (and previously requested) attribute we did miss earlier was preferred title, and possibly persona gender for any possible default title calculation.
https://bugs.launchpad.net/gratian/+bug/501223

Re the problems: If we remove the photo and social media link component, how much simpler does that make the project? Suddenly we have attributes that are within the realm of reason to maintained by canon because they don't change too often. And a number of them have clear official update sources rather than relying on individuals reporting things.

Teffania
p.s. I never got the impression you wanted to work for facebook....
p.p.s Back to the reminder - whatever is produced has to be maintainable code. Are you painting yourself into a corner again where no one else but you can fix this program? Is it a good idea to invest more time into a great program, but one that can't have minor issues tweaked (eg if royals create a new award style) due to lack of other programmers in the language if you fall under a bus?

For interest and comparison:
Page example from Anealan Op
http://aneala.sca.org.au/OP/person.asp?id=2
the concept of free text space for persona description is interesting

Personally, I think photos and stuff are generally going to be more work than blessing. Ok photos might be cool, but post implementing stuff like this - always a lot of data entry work. We don't want the short termism of facebook photos, but instead a phptp intended to last 10 years.  And then there is the isues of permission - we need the photographers's explicit permission to use the photo, and then it would be a very good idea to have the person in the photos permision to use that photo - a nightmare to chase up. And then there will be people who don't want to be identifiable by workmates for whom other scadians constantly pester sending in photos for.  Even with the theoretical team of data entry ppl and everyone uploading their photo in the correct format, how do we prove the person is the one with the rights to approve copyright on a photo or is the person in the photo?  Can of worms.

Re the problems: If we remove the photo and social media link component, how much simpler does that make the project?  Suddenly we have attributes that are within the realm of reason to maintained by canon because they don't change too often. And a number of them have clear official update sources rather than relying on individuals reporting things.

Teffania
p.s. I never got the impression you wanted to work for facebook.... 
p.p.s Back to the reminder - whatever is produced has to be maintainable code.  Are you painting yourself into a corner again where no one else but you can fix this program?  Is it a good idea to invest more time into a great program, but one that can't have minor issues tweaked (eg if royals create a new award style) due to lack of other programmers in the language if you fall under a bus?