Thanks alot for taking time to explain this. I have one more question but I guess it's better to make it another post since its quite different from what was asked here
From: Jerome Caffaro
Posted: 12/04/2013 13:15
Subject: WebSubmit Document Types
From: Jerome Caffaro
Posted: 12/04/2013 13:15
Subject: WebSubmit Document Types
Hi Bobby,
On 04/12/2013 11:39 AM, Bobby wrote:
> [...] I found it hard to understand the "Categories of Document Type
> REPORTS: " section of adding a document type. Which information is
> suppose to be contained here, should the input bare relation to
> collections regarding websearch admin collection tree? I
There is no relation between the categories and the collection. More
generally there is not a direct relation between a submission and a
collection.
From the "old" WebSubmit admin guide (and this should probably be
explicit in the new one too):
| On the relation between a search collection and a submission
| doctype:
|
| The relation between a search collection and a submission document
| type may be prone to certain confusion for Invenio administrators.
| This comes from the fact that there is no one-to-one direct mapping
| between them, as is usual elsewhere. The relation is more flexible
| than that.
|
| A search collection in Invenio is defined through a search query. For
| example, "all records where field F contains the value V belong to
| collection C". Several assertions can be deduced from this
| definition: 1/ A single record can appear in several collections. 2/
| There is no limitation to the number of collections in which a record
| can appear. 3/ Any query can be used to build a collection. The query
| can also be a complex one using logical operators, hence can rely on
| the value of several fields.
|
| (In addition, a search collection can be defined via a set of its
| subcollections in the hierarchy tree. Refer to the WebSearch Admin
| Guide for that matter.)
|
| The submission system basically creates an XML MARC record and stores
| it in the database. To which collection this new record belongs
| depends exclusively on the content of the XML MARC record. This XML
| MARC record is created by the Make_Record function. So the secret of
| the matching of a submitted record to a particular collection lies in
| the configuration of this function. Some examples will clarify this
| point:
|
| Example 1: Let's consider a "Preprints" collection which is defined
| by this query: "980__a:PREPRINT". We want to create a submission
| document type from which all records will go to this "Preprints"
| collection. For this, the Make_Record function should be configured
| so that a 980__a field containing "PREPRINT" will always be created.
| Example 2: Let's still consider the same "Preprints" collection, and
| an additional "Theses" collection based on a slightly different query
| "980__a:THESIS". We want to create a single submission type from
| which the records will go in the "Preprints" or "Theses" collections
| depending on a field chosen by the submitter. In this case, the
| Make_Record function should be configured so that a 980__a field will
| contain either "PREPRINT" or "THESIS" depending on the value entered
| by the submitter.
|
| The apparent disconnection between a submission document type and a
| search collection allows a great flexibility, allowing administrators
| to create 1 to 1, 1 to n, n to 1 or even 1 to 0 (not very useful!)
| relations.
<http://invenio-demo.cern.ch/help/admin/websubmit-admin-guide#oldwebsubmitguide>
In the end you are free to use the category information in whatever way
you like, and map that information to any MARC field of the created
records. You could even consider having such "categorization"
information within the submission form page instead, not "outside" on
the page "0".
You might also be interesting in having a look at the following
presentation on WebSubmit, given at the last Invenio User Group
Workshop:
<https://indico.cern.ch/contributionDisplay.py?contribId=7&confId=183318>
Finally please note that there are developments that should lead to the
"replacement" of WebSubmit (or let's say alternative) soon (hopefully).
<http://invenio-software.org/wiki/Development/Modules/WebDeposit>
Best regards
--
Jerome Caffaro ** CERN Document Server ** <http://cds.cern.ch/>
On 04/12/2013 11:39 AM, Bobby wrote:
> [...] I found it hard to understand the "Categories of Document Type
> REPORTS: " section of adding a document type. Which information is
> suppose to be contained here, should the input bare relation to
> collections regarding websearch admin collection tree? I
There is no relation between the categories and the collection. More
generally there is not a direct relation between a submission and a
collection.
From the "old" WebSubmit admin guide (and this should probably be
explicit in the new one too):
| On the relation between a search collection and a submission
| doctype:
|
| The relation between a search collection and a submission document
| type may be prone to certain confusion for Invenio administrators.
| This comes from the fact that there is no one-to-one direct mapping
| between them, as is usual elsewhere. The relation is more flexible
| than that.
|
| A search collection in Invenio is defined through a search query. For
| example, "all records where field F contains the value V belong to
| collection C". Several assertions can be deduced from this
| definition: 1/ A single record can appear in several collections. 2/
| There is no limitation to the number of collections in which a record
| can appear. 3/ Any query can be used to build a collection. The query
| can also be a complex one using logical operators, hence can rely on
| the value of several fields.
|
| (In addition, a search collection can be defined via a set of its
| subcollections in the hierarchy tree. Refer to the WebSearch Admin
| Guide for that matter.)
|
| The submission system basically creates an XML MARC record and stores
| it in the database. To which collection this new record belongs
| depends exclusively on the content of the XML MARC record. This XML
| MARC record is created by the Make_Record function. So the secret of
| the matching of a submitted record to a particular collection lies in
| the configuration of this function. Some examples will clarify this
| point:
|
| Example 1: Let's consider a "Preprints" collection which is defined
| by this query: "980__a:PREPRINT". We want to create a submission
| document type from which all records will go to this "Preprints"
| collection. For this, the Make_Record function should be configured
| so that a 980__a field containing "PREPRINT" will always be created.
| Example 2: Let's still consider the same "Preprints" collection, and
| an additional "Theses" collection based on a slightly different query
| "980__a:THESIS". We want to create a single submission type from
| which the records will go in the "Preprints" or "Theses" collections
| depending on a field chosen by the submitter. In this case, the
| Make_Record function should be configured so that a 980__a field will
| contain either "PREPRINT" or "THESIS" depending on the value entered
| by the submitter.
|
| The apparent disconnection between a submission document type and a
| search collection allows a great flexibility, allowing administrators
| to create 1 to 1, 1 to n, n to 1 or even 1 to 0 (not very useful!)
| relations.
<http://invenio-demo.cern.ch/help/admin/websubmit-admin-guide#oldwebsubmitguide>
In the end you are free to use the category information in whatever way
you like, and map that information to any MARC field of the created
records. You could even consider having such "categorization"
information within the submission form page instead, not "outside" on
the page "0".
You might also be interesting in having a look at the following
presentation on WebSubmit, given at the last Invenio User Group
Workshop:
<https://indico.cern.ch/contributionDisplay.py?contribId=7&confId=183318>
Finally please note that there are developments that should lead to the
"replacement" of WebSubmit (or let's say alternative) soon (hopefully).
<http://invenio-software.org/wiki/Development/Modules/WebDeposit>
Best regards
--
Jerome Caffaro ** CERN Document Server ** <http://cds.cern.ch/>
