⧼vector-jumptocontent⧽

Itemref field: Difference between revisions

From EPrints Documentation
mNo edit summary
mNo edit summary
Line 10: Line 10:
*** [[Itemref field]]
*** [[Itemref field]]


== Properties ==
== Additional Properties ==
As for [[Int field]]s with the following differences...
As for [[Int field#Additional_Properties|Int fields]] except for:


{| border="1" cellpadding="3" cellspacing="0"
{| border="1" cellpadding="3" cellspacing="0"
Line 20: Line 20:


== Required Phrases ==
== Required Phrases ==
No additional phrases.
No additional phrases beyond those required for [[Int field#Required_Phrases|Int fields]].


== Database ==
== Database ==
Itemref fields are stored in the database as
Itemref fields are stored in the database as
  fieldname INT(11)
  fieldname INT(11)



Revision as of 10:06, 9 April 2023


Description

This field allows another data object to be referenced, which belongs to a specified datasetid.

Inheritance

Additional Properties

As for Int fields except for:

name default description
datasetid n/a This property is always required.

Required Phrases

No additional phrases beyond those required for Int fields.

Database

Itemref fields are stored in the database as

fieldname INT(11)

API

See API page.

Examples

Most basic example.

{
    name => 'userid',
    type => 'itemref',
    datasetid => 'user',
},

To specify one eprint succeeds another. This may not always be required and if you clone the eprint record the new eprint should not succeed the same eprint.

{
    name => 'succeeds', 
    type => 'itemref',
    required => 0,
    datasetid => 'eprint', 
    can_clone => 0,
}

You might create a data object that groups together several eprints

{
    name => 'items',
    type => 'itemref', 
    datasetid => 'eprint', 
    multiple => 1, 
    required => 1,
}