026500

 

BELIEF

Bringing Europe’s eLectronic Infrastructures to Expanding Frontiers

 

 

WP1D4.2.c – The BELIEF DL User Guide “At a Glance”

Ver. 1.1

 

09 January 2007

 

 

Start date: 1 November 2005                                                                             Duration: 24 months

 

The BELIEF Consortium consists of:

1.      Metaware SpA, IT

2.      CNR- ISTI, IT

3.      University of Athens, GR

4.      ERNET, IN

5.      ENGITECH, IE

6.      Escola Politécnica da Universidade de São Paulo, PUSP, BR

7.      Wisconsin-Madison University, US

Responsible Author:

Franco Zoppi - CNR-ISTI, IT

Contributors:

-

Status:

Confidentiality:

[

[

[

[

 

 

 

X

 

]

]

]

]

Draft

To be reviewed

Proposal

Final/Released to CEC

[

[

 

[

 

 

[

X

 

 

 

 

 

 

]

]

 

]

 

 

]

- PU

- PP

 

- RE

 

 

- CO

for PUblic use

restricted to other Programme Participants (including the Commission Service)

REstricted to a group specified by the consortium (including the Commission Service)

COnfidential, only for members of the consortium (including the Commission Service)

Summary / Content:

WP1D4.2.c - T1.2 – The BELIEF DL User Guide “At a Glance”.

 

 

Contents

 

1.     Summary. 4

2.     User Functionality. 5

2.1.   Community. 5

2.1.1.   My actions. 5

2.1.2.   User management (for DL Administrators only) 5

2.1.3.   Groups. 5

2.1.4.   Document management 5

2.2.   Information Space. 6

2.2.1.   Manage. 6

2.2.2.   View.. 6

2.2.3.   Personal 6

2.3.   Search. 9

2.3.1.   Search type. 9

2.3.2.   Search options. 10

2.3.3.   Result set 11

2.4.   Browse. 12

2.4.1.   Browse type. 12

2.4.2.   Browse options. 12

3.     Author Functionality. 13

3.1.   Options for Authors. 13

3.2.   New documents. 13

3.3.   New editions of already published documents. 13

3.4.   Correction of already published documents. 13

3.5.   Withdrawal requests. 14

4.     Reviewer & Administrator Functionality. 15

4.1.   Options for Reviewers. 15

4.2.   Options for Administrators. 15

4.2.1.   Submission Requests. 15

4.2.2.   Edition Requests. 16

4.2.3.   Correction Requests. 17

4.2.4.   Withdrawal Requests. 17

5.     References. 18

 

 


 

Log of changes

 

Version N°

Date (dd/mm/yyyy)

Changes

0.1

05/09/2006

None – First draft.

1.0

11/09/2006

General revision and update of content.

1.1

09/01/2007

Final version following the recommendations of the 1st Annual Review.

 

 

1.                Summary

The BELIEF Digital Library is accessible from the BELIEF Portal clicking on the
Digital Library>Expert Interface menu or directly at
http://belief02.isti.cnr.it/.

The Digital Library Interface is organised in work environments (HOME, COMMUNITY, INFORMATION SPACE, SEARCH, BROWSE) which in their turn are organised according to different menus. This User Guide is presented under the following three Sections, according with the roles a community member can play:

o       User Functionality

o       Author Functionality

o       Reviewer & Administrator Functionality

This User Guide “At a Glance” is derived from the complete User Guide in [WP1D4.2b].

 

2.                User Functionality

2.1.         Community

This environment allows any user to access the DL as a “registered user” (entering Login and Password) or to register by completing the form displayed by the system (data tagged with a red asterisk are mandatory). Registered users may be entitled to different access rights.

The menus of the Community environment can be accessed by registered users only.

2.1.1.      My actions

q       Personal Data

·        View Profile shows the user “profile” data

·        Edit user data updates user data

·        Unregister deletes user name from the DL register

q       Logout stops the user operating as a “registered user”

2.1.2.      User management (for DL Administrators only)

q       View all users allows the DL Administrator to manage users’ access rights

2.1.3.      Groups

Is used to create work groups and share information.

 

q       New defines a new group. The user is requested to enter a Name identifying his/her group, a Description (optional) and to create either a “public” group, accessible by all users (option YES) or a non-public group (NO). The “CREATE” button terminates the operation and “CLEAR” button cancels all entered data.

q       View

·        Public Groups  lists all “public” groups. Each group description contains the address of the group administrator, so that users can request further information in order to become associated  with that group.

·        My groups allows group administrators or group members to list “their” groups. For any administrator, the display also includes the following  buttons:

o       ADD USER(S) – to include other users in the group.

o       ADD COLLECTION(S) – to associate virtual collections with the group.

o       DELETE – to cancel the whole group.

2.1.4.      Document management

For Management by Authors: see Section 3.
For Management by Reviewers & Administrators: see Section
4.

 

2.2.         Information Space

This work environment can be used by any user (registered or not) to define  his/her information space. The user’s information space is composed of all collections the user has selected from those managed by the DL. If no information space is defined, user operations are executed on all “Public collections”, which are visible through the “VIEW” menu.

2.2.1.      Manage

Is used to insert/delete collections in/from the user’s information space.

q       Select is used to choose collections for the information space according to the following options:

·        From public collections lists all public collections and gives information through the link “details” which is associated with each collection. It is worth noting that collections marked by the symbol + are structured in sections which are displayed by clicking on  that symbol.

A collection can be selected clicking on the corresponding “add” button.

The names of the selected collections appear in the “Selected collections” box. When the selection ends, the information space is registered by clicking on the ADD TO SPACE button: all selected collections are inserted in the user’s information space (and added to those already present, if any). The operation concludes with the display of the current information space composition.

·        From personal collections [for registered users only] is used to select collections associated with groups where the user is either the administrator or a member. The selection can be made as described in the “From public collections” option.

q       Remove deletes collections from their information space. Collections are listed and the user can delete them all with the REMOVE button.

2.2.2.      View

q       Public collections displays all public collections which are available to generic users.

q       Personal Collections [for registered users only] displays those collections which are associated with groups where the user is either the administrator or a member.

q       Current information space displays the information space components at the current time.

2.2.3.      Personal

Allow to create/delete personal (virtual) collections (accessible to authorized users only).

 

q       Create collection: A personal collection can be created starting either from scratch, i.e. from archives of publishing institutions, or from a pre-existing collection, as follows:

a)       Create from scratch: if this option is selected, the NEXT STEP button displays the form “Insert your collection data” (see below).

b)      Inherit an existing collection: if this option is selected, the NEXT STEP button opens the window entitled “Do you want to inherit from” and the user can choose between the following options:

·        a public collection

·        a personal collection

In either case, the NEXT STEP button opens the form “Select a collection to inherit”, which lists the collection selections (either public or personal) according to user interest. (for each collection, the “details” link causes the description of the collection to appear). After the selection, the NEXT STEP button opens the form “Insert your collection data” (see below).

c)       Grouping existing collections: if this option is selected, the NEXT STEP button displays the form “Insert your collection data” (see below).

d)      Create collections from Repository’s Sets: if this option is selected, the NEXT STEP button opens the window entitled “Please select the set(s) the collection is created from” and the user is shown the list of all available collections that can be selected.

After the selection, the NEXT STEP button opens the form “Insert your collection data” (see below).

 

Insert your collection data”

The only restriction on the data is the length that can be inserted in the fields “Name”, “Subject” and “Description”.

The “Metadata format” field is used to select the metadata for imposed selection conditions.

The “Filtering name and value” field can be used to select the documents to be inserted in the collection according to the value of a metadata element. The default element is “language” (but this configuration can be changed at system installation).

The NEXT STEP button introduces the form:

 

“Now you have to define a condition for your collection”

that guides the user to create his/her collection through the following operations:

1.  Select the authorities in which your condition will search: In case a), i.e. when the collection is created from scratch, all authorities are displayed for selection; in case b), i.e. when an existing collection is inherited, only the authorities of that collection are displayed.  If no selection is made, the search for documents to be included in the collection will be made on all authorities. After selection, the ADD button transfers the selected authority into the user’s personal space; the opposite operation can be made with the REMOVE button after selecting an authority in the user’s personal space. Both operations can be repeated.

2.  Define your condition. The selection criteria is expressed by defining the condition (SINGLE CONDITION option) or the conditions (MULTIPLE CONDITIONS option) the document metadata have to satisfy in order to be included in the collection. In the first case, the user chooses both the metadata element on which to set the condition (Dublin Core metadata, if not otherwise set) and the operator, and enters the appropriate value in the data field according to the format suggested by the system. The CLEAR button  resets the form.

The operators in the “Select operator” menu have the following meanings:

o       contain: the metadata element must contain one or more of the terms entered in the data field.

o       equal: the character string in the metadata element must be exactly equal to the character string entered in the data field.

o       phrase: the metadata element must contain one or more terms of the phrase entered in the data field, in any order.

o       equal/greater-than/greater-equal/less-than/less-equal: the metadata element must contain a value that is equal to/greater than/greater than or equal to/less than/less than or equal to the value entered in the data field.

If the option “MULTIPLE CONDITIONS” is chosen, a form guides the user to structure conditions as a pair of conditions linked by an operator (selectable in the SELECT window). The mechanism repeats every time the user selects the option “MULTIPLE CONDITIONS”.

The “Select” menu offers the well-known Boolean operators “And”, “Or”, “And-Not” and the following operators that make it possible to use a metadata element as a “filter”:

o       filter-accept: all document satisfying both conditions of the pair are searched; differently from what happens with the “And” operator,  results are ordered by the “degree of correspondence” to the first condition.

o       filter-reject: all document satisfying the first condition and not-satisfying the second condition of the pair are searched; differently from what happens with the “And-Not” operator, results are ordered by the “degree of correspondence” to the first condition.

The process concludes by clicking on the FINISH button. The user can validate the conditions set to create the collection and choose from:

o       DEFINE A NEW CONDITION (back to Step 1 above)

o       DISCARD COLLECTION

o       SAVE COLLECTION

 

q       Delete collection lists user’s personal collections; any collection can be deleted with the corresponding DELETE button.

 

2.3.         Search

Selection of this environment gives immediate access to the form for Simple Search. Queries can be freely expressed and searches are executed on all elements of document metadata. (Other kinds of search - Advanced, Relevance Feedback - are available in the SEARCH TYPE menu). In the event of a lengthy search, a signal appears providing an estimate of the time required to perform the search.

Display of search results

Descriptions of documents resulting from the search are displayed. The “Previous” and “Next” buttons are used to scroll up and down the screen. Descriptions are ordered by the “degree of correspondence” to the query according to probability criteria. The degree of correspondence (Rank) is indicated both as a percentage and graphically.

Each description is associated with four (?) buttons - “ View this document”, “Mark as relevant”, that operate as follows:

q       View this document makes the following information appear on the screen:

o       Document Identifier

o       Document Metadata

o       Document Manifestations i.e., the diverse formats for a created document or a document section , e.g. a text in Post-Script, PDF, PowerPoint, etc., or an image in GIF, JPEG, etc.. The user can choose the format by clicking on its icon: the document file is then transferred from its deposit archive to the user’s machine.

q       Mark as relevant is used to mark documents considered to be relevant. This allows the user to activate the “Relevance Feedback” search type, which is based on the contents of such documents. The relevance feedback search option can be selected in the SEARCH TYPE menu.

2.3.1.      Search type

q       Simple search: here queries can be freely expressed and searches are executed on all metadata elements. The SEARCH button starts the search. In the event of a lengthy search, a signal appears providing  an estimate of the time required to perform the search. Results appear as described above.

q       Advanced search is used to impose one or more conditions on one or more elements of  metadata. If the “single condition “ option is chosen, both metadata elements and operators can be selected from the appropriate menus (Dublin Core metadata are used by default, but a different system configuration is possible).

The operators in the “Select operator” menu have the following meanings:

·        contain: the metadata element must contain one or more terms of the search query; descriptions are ordered by the “degree of correspondence” to the query according to probability criteria.

·        equal: the character string in the metadata element must be exactly equal to the search query.

·        phrase: the metadata element must contain one or more terms of the search query, in any order; descriptions are ordered by the “degree of correspondence” of the query according to the probability criteria.

The CLEAR button resets the form. The SEARCH button starts the search.

If the option “Multiple conditions” is chosen, the user is guided to structure the query as a pair of conditions bound together by an operator (that can be selected from the “select” window). This mechanism is activated every time the user selects the “Multiple condition” option. The system advises the query format required for the selected metadata element.

The “Select” menu offers the well-known Boolean operators “And”, “Or”, “And-Not” and the following operators that make it possible to use a metadata element as a “filter”:

·        filter-accept: all document satisfying both conditions of the pair are searched; differently from what happens with the “And” operator; results are ordered by the “degree of correspondence” to the first condition.

·        filter-reject: all document satisfying the first condition and not satisfying the second condition of the pair are searched; differently from what happens with the “And-Not” operator;  results are ordered by the “degree of correspondence” to the first condition.

The CLEAR button resets the form. The SEARCH button starts the search. In the event  of a lengthy search, a signal appears providing  an estimate of the time required to perform the search. Results appear as described above.

q       Relevance feedback This option appears only when one or more documents resulting from a search have been marked – see the description of the Mark as relevant button above]. The SEARCH button starts the search. In the event of a lengthy search, a signal appears providing an estimate of the time required to perform the search. Results appear as described above.

2.3.2.      Search options

q       Configure search defines search parameters differently from the default parameters. The configuration that the user selects will be ignored by the system if it is not compatible with the metadata of the collections the user has inserted in  his/her information space.

q       Simple The “simple” search can be configured for:

o       Metadata format. Documents are catalogued with multiple metadata sets: the DUBLIN CORE set - used by default - and the OLAP set – an extension of the D.C. metadata set defined specifically for the OpenDLib system - are always present.

o       Filtering name and value. This filter can be used to select the documents resulting from the search according to the value of a metadata element. The default element is “language”, but this configuration can be changed at system installation.

If no configuration is stipulated by the user, the search is carried on Dublin Core metadata, without any filter.

The CONFIRM button displays the parameters of the user-stipulated configuration. The DEFAULT VALUES button resets default configurations.

q       Advanced The “advanced” search can be configured for:

o       Metadata format. Documents are catalogued with multiple metadata sets: the DUBLIN CORE set - used by default - and the OLAP set - a metadata set defined specifically for the OpenDLib system - are always present.

o       Filtering name and value. This filter can be used to select the documents resulting from the search according to the value of a metadata element. The default element is  “language”, but this configuration can be changed at system installation.

If no configuration is stipulated by the user, search is carried out on Dublin Core metadata, without any language filter.

The CONFIRM button displays the parameters of the user-stipulated configuration. The DEFAULT VALUES button resets default configurations.

q       Configure result page is used to configure each type of search with respect to the display of the results:

·        The number of documents for each page (<100).

·        The presentation of the documents: the user can choose among different levels of description (Header, Long, Short).

The CONFIRM button registers and displays the selections made by the user. The DEFAULT VALUES button resets the default configurations.

q       View details shows the “current” search parameters: those corresponding to the “default” values or those of the user-stipulated configurations.

2.3.3.      Result set

q       Get Last is used to return to the page where the results of the last search operation are displayed.

q       Print page prints the page where the results are displayed.

 

2.4.         Browse

In the BROWSE environment, the content of a collection (that included in the user’s information space) can be examined in different ways (see BROWSE TYPE). By selecting this environment a new form appears and can be used to:

·        Organise all documents in alphabetical order on the basis of the metadata element value, (field) which can be selected from the menu.

·        Define the portion of alphabetical order the user wants to see (the format of the data to be inserted in the “from” and “to” fields has to correspond to the format indicated near the chosen metadata element - for example the format YYYYMMD(D) is to be used).

The BROWSE button activates the sorting operations.  In the event of a lengthy search, a signal appears providing  an estimate of the time required to perform the search.

Display of search results

Documents descriptions are displayed in the user-defined format. The “Previous” and “Next” buttons are used to scroll up and down the screen pages. The following buttons are associated with each description:

q       View this document makes the following information appear on the screen:

o       Document Identifier

o       Document Metadata

o       Document Manifestations: i.e., the diverse formats for a created document or a document section; e.g. a text in Post-Script, PDF, PowerPoint,… ; or an image in GIF, JPEG,…; The user can choose the format by clicking on its icon: the document file is then transferred from its deposit archive to the user’s machine.

q       Mark as relevant is used to mark documents considered to be relevant. This allows the user to activate the “relevance feedback” search type, which is based on the contents of such documents. The relevance feedback search option can be selected in the SEARCH TYPE menu.

2.4.1.      Browse type

q       Custom           Browses the descriptions of the documents in the collection.

q       Standard         Browses the indexes created on the collection metadata.

2.4.2.      Browse options

q       Select Format is used to define the metadata set for the basis of order criteria. (different from that used by the system “default”)

q       Configure result page is used to configure each type of search with respect to the display of the results:

·        The number of documents for each page (<100).

·        The presentation of the documents: the user can choose among different levels of description (Header, Long, Short).

The CONFIRM button registers and displays the selections made by the user. The DEFAULT VALUES button resets the default configurations.

q       View details Shows the “current” search parameters: those corresponding to the “default” values or those of the user-stipulated configurations.

 

3.                Author Functionality

3.1.         Options for Authors

Community>Docs Management>Submit opens your working area - Submission Mode – where the following types of documents to the Library Administrator can be submitted:

·        New documents

·        New editions of documents already published

·        Correction of documents already published

·        Withdrawal requests

3.2.         New documents

Create a new document in order to submit it for publication; Edit or Remove a document in preparation, if any (documents in preparation are those that have been started but did not finish the creation procedure; these documents are identified with a temporary identification number).

Please consider the following:

·        Click the link Create New Document to create a new document. A page where a menu to select the Authority for the document to be published will then open. Then click the NEXT button. A special page is presented to choose which model the document has to conform to. Depending on which authority is chosen, all or a set of the document models listed below are presented for selection.

Select a model and click the NEXT button. Then follow the instructions given under the model selected.

·        Click the link Submit when finished creating/editing the document.  A message will require the selections to be validated.

·        Click the link Remove to delete a document in preparation. A message will require the selections to be validated.

·        Click the link Edit to open a page to update a document in preparation.

3.3.         New editions of already published documents

This procedure creates a new edition of an already published document while maintaining the original. Click the link, select a document to display the list of your already published documents, if any. Select the document to edit, thus making it appear in your working Area where it will remain “in preparation”.. Click the link Edit to open the Edit-page. The Edit-page shows the Document Structure, i.e. the structural elements of the selected document, and the editing operations described in Sections 1.1 to 1.5 for the different models, depending on which model the document conforms to

Remove any of them with the corresponding link. The Submit link concludes the procedure.

3.4.         Correction of already published documents

This procedure replaces an already published document with a corrected version of it. Click the link, select a document to display the list of already published documents, if any. Select the document to be corrected. The ID of the selected document will be called “in preparation” as long as it is being worked on. All documents in preparation are listed in the user’s Working Area. Click the link Edit corresponding to any of them to open the Edit-page. The Edit-page shows the Document Structure, i.e. the structural elements of the selected document,  and the editing operations described in Sections 1.1 to 1.5 for the different models, depending on which model the document conforms to. Remove any of them with the corresponding link. The Submit link concludes the procedure.

3.5.         Withdrawal requests

Click on the Create New Request link to display the list of already published documents, if any. Select the document to withdraw and complete the request form that will appear. Then click on the NEXT button. The request will be listed in the grew bar: here it is possible to Remove or Submit it to the Library Administrator or View the document the request refers to. Click on the View link to make the Document Structure elements to appear (if the structure tree is not shown, then click on Document Structure to display it). Each element of the Document Structure is composed by two pieces of information, namely: i) the name of that structural element  and ii) the type of its manifestation (i.e. which file type represents its content). Click on any manifestation to display it.

 

4.                Reviewer & Administrator Functionality

4.1.         Options for Reviewers

Community>Docs Management>Review opens the user’s working area - Review Mode - and displays the list of the authorities from which submission requests have come. Select an authority and click the select button  to see the list of the documents to be reviewed.

For any document:

·        View this document: makes the Document Structure elements appear (if the structure tree is not shown, then click on Document Structure to display it). Each element of the Document Structure is composed by two pieces of information, namely: i) the name of that structural element  and ii)  the type of its manifestation (i.e. which file type represents its content). Click on any document manifestation to display it.

·        Make your review: makes a review form to appear which is headed by the document temporary ID. Complete the form and click on the submit review  button: this compiles the evaluation report for the DL Administrator.

·        Show other reviews; here reviews by other reviewers, if any, can be viewed.

4.2.         Options for Administrators

Community>Docs Management>Admin opens a page that displays, in table form, the amount of different submission request types from the different authorities - Submissions, Editions, Corrections, Withdrawals

This page also allows to update the default option regarding whether Email confirmation of Administrator’s decisions are to be sent or not.

a)      Click directly on any red numeral in the table to see the detailed description of the documents related to the corresponding authority and the corresponding request.

b)      Click the name of the authority interested in to see its description. At the same time, all the information related to that authority appears on the left-hand side of the window in a short form. Here, click on the red numeral to see the detailed description of the documents related to the corresponding authority and the corresponding request; or return by clicking the link Return to Admin Page.

A list of document descriptions appears and is possible to operate on any described document with different actions depending on the type of request, as detailed below.

4.2.1.      Submission Requests

New

Documents in this page are described with their i) handle and title; ii) author; iii) number of reviews requested vs. reviews received; iv) date; v) model.

Documents can be:

a)      Collectively managed as follows:

o       They can be selected according to their model through the Model menu.

o       They can be individually selected or selected through the select all button. Selections can be cancelled through the select none button.

o       Selected documents can be composed into a new document through the create document from selection button. After clicking this button, it is mandatory to choose which model, - whether journal or book or proceedings -  the new created document has to conform to. After selection, the description of the new document is displayed. Click the Return to New Submissions button to return to the New Submission Requests page, where the new created document is listed and can individually be managed as described in (b) below.

 

b)      Individually managed through the following operations:

o       View doc: makes the Document Structure elements appear (if the structure tree is not shown, then click on Document Structure to display it). Each element of the Document Structure is composed by two pieces of information, namely: i) the name of that structural element and ii) the type of its manifestation (i.e. which file type represents its content). Click on any document manifestation to display it.

o       Edit doc: links to the Edit page. The structure of the document is displayed and the editing operations described in Sections 1.1 to 1.5 for the different models, depending on which model the document conforms to.

o       Evaluation: displays which evaluation has been given by the reviewers (if any); otherwise  the message “No reviewer” is displayed.  The following actions are made available by the corresponding buttons:

·        Approve: opens a window where it is mandatory to give the document the appropriate ID and associate it to one or more document collections. Then click on the accept button.

·        Reject: rejects the document while giving the user notice of this.

·        Discard: deletes the document while giving the user notice of this.

·        Choose reviewers: opens a window to select the reviewer/s; then click on the accept button. Additional reviewers can be selected at later times.

Rejected

The user has the following options:

·        View this document: makes the Document Structure elements appear (if the structure tree is not shown, then click on Document Structure to display it). Each element of the Document Structure is composed by two pieces of information, namely: i) the name of that structural element  and ii) the type of its manifestation (i.e. which file type represents its content). Click on any document manifestation to display it.

·        Edit this document: links to the Edit page. The structure of the document is displayed and the editing operations described in Sections 1.1 to 1.5 for the different models, depending on which model the document conforms to.

·        Unreject this document: returns the document in the New Submission Requests group.

·        Discard this edition: deletes the document while giving the user notice of this.

4.2.2.      Edition Requests

New

The user has the following options:

·        View this edition: makes the Document Structure elements appear (if the structure tree is not shown, then click on Document Structure to display it). Each element  of the Document Structure is composed by two pieces of information, namely: i) the name of that structural element  and ii) the type of its manifestation (i.e. which file type represents its content). Click on any document manifestation to display it.

·        Edit this edition: links to the Edit page. The structure of the document is displayed and editing operations described in Sections 1.1 to 1.5 for the different models, depending on which model the document conforms to.

·        Approve this edition: the document is approved for publication: its ID is updated with the version number.

·        Reject this edition: the document is deleted and the user is given notice of this.

·        Discard this edition: deletes the document while giving the user notice of this.

Rejected

The user has the following options:

·        View this edition: makes the Document Structure elements appear (if the structure tree is not shown, then click on Document Structure to display it). Each element  of the Document Structure is composed by two pieces of information, namely: i) the name of that structural element  and ii) the type of its manifestation (i.e. which file type represents its content). Click on any document manifestation to display it.

·        Edit this edition: links to the Edit page. The structure of the document is displayed and the editing operations described in Sections 1.1 to 1.5 for the different models, depending on which model the document conforms to.

·        Unreject this edition: returns the document in the New Edition Requests group.

·        Discard this edition: deletes the document while giving the user notice of this.

4.2.3.      Correction Requests

The user has the following options:

·        View this document: makes the Document Structure elements appear (if the structure tree is not shown, then click on Document Structure to display it). Each element  of the Document Structure is composed by two pieces of information, namely: i) the name of that structural element  and ii)  the type of its manifestation (i.e. which file type represents its content). Click on any document manifestation to display it.

·        Edit correction: links to the Edit page. The structure of the document is displayed and the editing operations described in Sections 1.1 to 1.5 for the different models, depending on which model the document conforms to.

·        Approve correction: the corrected document replaces the existing one.

·        Reject correction: the corrected document is rejected and the user is given notice of this.

4.2.4.      Withdrawal Requests

The user has the following options:

·        View this document: makes the Document Structure elements appear (if the structure tree is not shown, then click on Document Structure to display it). Each element of the Document Structure is composed by two pieces of information, namely: i) the name of that structural element  and ii) the type of its manifestation (i.e. which file type represents its content). Click on any document manifestation to display it.

·        Reject withdrawal: the withdrawal of the document is rejected and the user is given notice of this.

·        Approve withdrawal: the withdrawal of the document is approved, the document is “logically” deleted and the user is given notice of this.

·        Delete document from repository: after the withdrawal request has been approved, the document can be “physically” deleted.

 

5.                References

 

 

[DCMI]                The Dublin Core Metadata Initiative Open Forum

                                      http://www.dublincore.org/

[DCMIMT]          DCMI Metadata Terms

http://dublincore.org/documents/dcmi-terms/

[DCT1]                DCMI Type Vocabulary. DCMI Recommendation

                            http://dublincore.org/documents/dcmi-type-vocabulary/

[DoW]                 Project BELIEF Annex I – “Description of Work”

[ISO639]             ISO 639-2 - Codes for the representation of names of languages

                            http://www.loc.gov/standards/iso639-2/langhome.html

[RFC3066]          Tags for the Identification of Languages, Internet RFC 3066.

                            http://www.ietf.org/rfc/rfc3066.txt

[OpenDLib]          http://www.opendlib.com

[SAV]                  https://gna.org/projects/savane

[TGN]                  Getty Thesaurus of Geographic Names

                            http://www.getty.edu/research/tools/vocabulary/tgn/index.html

[W3CDTF]          Date and Time Formats, WRC Note

                            http://www.w3.org/TR/NOTE-datetime

[WP1D4.2.a]       BELIEF DL Release Notes – Release 2.0

[WP1D4.2.b]       BELIEF DL User Guide