Author Topic: Alpha Release: Discussion, Feature Requests, etc  (Read 480 times)

Jubal

  • Megadux
    Executive Officer
  • Posts: 22494
  • Karma: 102
  • Awards Awarded for oustanding services to Exilian!
    • View Profile
    • Awards
Alpha Release: Discussion, Feature Requests, etc
« on: January 22, 2016, 03:06:42 PM »
The current live alpha is here:
http://www.exilian.co.uk/academy/cpp/index.php

Do say what extra you'd like to see done and discuss how you're finding the system so far by posting here :)
The duke, the wanderer, the philosopher, the mariner, the warrior, the strategist, the storyteller, the wizard, the wayfarer...

Glaurung

  • Basileus
    Head of Staff
  • Posts: 2335
  • Karma: 11
    • View Profile
    • Awards
Re: Caucasian Prosopography Project Alpha Release
« Reply #1 on: January 29, 2016, 01:41:26 PM »
I've had a quick play with the search form; here are some thoughts.

Firstly, it seems quite robust :) I tried various combinations of characteristics and it always behaved cleanly - there were no pages with obscure SQL errors.

I suggest splitting the search characteristics into groups:
- nationality / ethnicity (Georgian, Armenian, byzantine etc.)
- role or rank (ruler, general, bishop etc.)
- religion
- pronouns / gender
This would make it more obvious why "Armenian" appears twice.
Also, it's not obvious why "Georgian Royalty" is a distinct characteristic - would this not be "Georgian" and "ruler"? Or should there be a general role of "royalty" that could be used for the members of royal families of any political/ethnic entity?

I tried searching with nothing ticked, and got no results back. I was more than half-expecting this, but I wondered whether it would give me all records instead of none. I presume there is no means of requesting all the records at the moment.

I tried searching with all the ethnicity characteristics ticked, and still got nothing. I was a bit more surprised by this - I thought it more likely that I would get all the records this way. I assume the underlying code is using AND to join each of the ticked characteristics for the search, even when they are in the same group. I suspect OR for joins within a group, and AND for joins between groups, is likely to be more intuitive.