This is an example search for a song. There will be many different ideas about what should be in the song's attributes.
KendraBase should be able to cope with all.
Interesting things:
- Sometimes there is no need for explicit units as the user will input values in a specific format which can be directly interpreted - like with a date.
- But we could write a date as 21/01/2004 or 20040121 or have a series of drop down menus for day, month and year. Both interpreted text and drop down menus should be possible using example below. Drop down menu could be:
- Date Recorded, Time, Day_Units, Month_Units, Year_Units
Search for:
The Attributes have 3 columns: the name, the type of operators used and the unit menu to put in the query builder.
Attributes:
- Album, Text, None
- Artist, Text, None
- BPM, Number, BPM_Units
- Bit Rate, Number, File_Transfer_Rate_Units
- Comment, Text, None
- Composer, Text, None
- Date Recorded, Time, Time_Input
- Date Added, Time, Time_Input
- Genre, Text, None
- Cost, Number, Currency_Units
- Duration, Number, Time_Units
- Song, Text, None
- Track, Number, None
- Lyrics, Text, None
Text:
- is equal to, A
- is not equal to, A
- contains, A
- does not contain, A
- starts with, A
- does not start with, A
- ends with, A
- does not end with, A
Number:
- is equal to, A, Units
- is not equal to, A, Units
- is greater than, A, Units
- is not greater than, A, Units
- is less than, A, Units
- is not less than, A, Units
- is in the range, A, Units, to, B
- is not in the range, A, Units, to, B
Time:
- is equal to, A, Units
- is not equal to, A, Units
- is after, A, Units
- is not after, A, Units
- is before, A, Units
- is not before, A, Units
- is in the range, A, Units, to, B, Units
- is not in the range, A, Units, to, B, Units
- is in the last, A, Units
- is not in the last, A, Units
Time_Units:
- seconds
- minutes
- hours
- days
- weeks
- months
- years
BPM_Units:
File_Transfer_Rate_Units:
Currency_Units:
![[Home]](/graphics/kendra-small.gif)
KendraBaseQueryBuilderExampleSong