Difference between revisions of "Request Object"
| Line 1: | Line 1: | ||
| + | {{reference}} | ||
| + | {{dataobj}} | ||
| + | |||
The Request object encapsulates a single request for a document, which can be: | The Request object encapsulates a single request for a document, which can be: | ||
Revision as of 18:10, 10 January 2007
EPrints 3 Reference: Directory Structure - Metadata Fields - Repository Configuration - XML Config Files - XML Export Format - EPrints data structure - Core API - Data Objects
EPrints 3 Reference: Directory Structure - Metadata Fields - Repository Configuration - XML Config Files - XML Export Format - EPrints data structure - Core API - Data Objects
Data Objects: Access - Document - EPrint - Event Queue - File - History - Import - Login Ticket - Request - Saved Search - Subject - User
The Request object encapsulates a single request for a document, which can be:
- a specific (restricted) document in the repository
- a document not in the repository (where a record has no documents attached)
Built in Fields
| Field Name | Type | Description |
|---|---|---|
| requestid | int field | |
| eprintid | itemref field eprint | The ID of the record |
| docid | text field | The ID of the document requested |
| datestamp | time field | When the request was made |
| userid | itemref field user | The ID of the user who can respond to the request (if email matches a registered user) |
| text field | The email the request was sent to | |
| requester_email | text field | The email of the person who requested the document |
| reason | longtext field | The reason that the request was made, if any |
