Specifications for the Wordspotting
From Armarius
[edit] Specifications (03/08/07)
When a user is connected, he will be able to see :
- The default views
- The views of his group
- His personalized views
And, for a view, if he has the right to modify it, he can launch wordspotting sessions on it.
So, we will have to introduce the notion of two types of transcription : the validated transcriptions (when the user has seen the wordspotting results and has validated the transcriptions found) and the non-validated transcriptions (the user has seen the wordspotting results but hasn't validated the transcriptions found). And we will need a new table : armarius_wordspotting with the fields : ws_user_id, ws_date, ws_state, ws_text, ws_view_id, ws_du_id. ws_user_id is the id of the user who launches the wordspotting session. ws_date is the date of the launching of the wordspotting session. ws_state will be "Started" (if the wordspottig session is started, but not finished), "Finished" (if the wordspotting session is finished but the user hasn't validated the transcriptions), or "Validated" (if the wordspotting session is finished but the user has validated the transcriptions). ws_text is the value of the transcription to find in the wiew with the wordspotting. ws_view_id is the view on what the wordspotting is launched. The wordspotting only concerns the pages which are in the view. ws_du_id is the information of the du of the transcription to find with the wordspotting.
When a wordspotting session is finished, the user will be able to see the results, and to choose if he wants to validate the transcriptions found. He would have a button to select to validate a certain number of transcriptions found for each page of the view. If he chooses to validate, the transcriptions found will be inserted into the table armarius_annotation with anno_meta_type equal to 14 and then will be visible in the view ; if he chooses to invalidate, the transcriptions found will be inserted into the table armarius_annotation with anno_meta_type equal to 13 and wont't be visible in the view.
We will also modify the table armarius_du which will have the fields : du_id, du_type, du_value. du_type will be "collection", "view", "page" or "fragment of page". du_value depends on du_type. If du_type is "collection", du_value will be the id of the collection. If du_type is "view", du_value will be the id of the view. If du_type is "page", du_value will be the id of the page. If du_type is "fragment of page", du_value will be the 4 coordinates separated by a separator defined in config.php.
