ICAT Metadata

The following page details what metadata is inserted into ICAT to accommodate user uploads for:

  • Dataset

  • Datafile

Dataset

Cardinality

Class

Populated

Cardinality

Class

Populated

0,1

Sample

N/A

1,1

Investigation

Yes

0,*

DatasetTechnique

N/A

0,*

Datafile

N/A

0,*

DatasetParameter

N/A

1,1

DatasetType

Yes (would need to create a new one for uploaded data)

0,*

DataCollectionDataset

N/A

0,*

DatasetInstrument

N/A

Field

Type

Populated

Field

Type

Populated

name

String [255] NOT NULL

Yes, user provided

location

String [255]

No

complete

boolean NOT NULL

No

startDate

Date

No

doi

String [255]

No

createId

String

Yes (auto; simple/root)

fileSize

Long

No, but an SQL trigger in ICAT sets this

createTime

Date

Yes (auto)

modTime

Date

Yes (auto)

description

String [255]

Yes, user provided

fileCount

Long

No, but an SQL trigger in ICAT sets this

modId

String

Yes (auto)

endDate

Date

No

Datafile

Cardinality

Class

Populated

Cardinality

Class

Populated

0,*

RelatedDatafile

N/A

0,*

DatafileParameter

N/A

0,1

DatafileFormat

N/A

1,1

Dataset

Yes

0,*

RelatedDatafile

N/A

0,*

DataCollectionDatafile

N/A

Field

Type

Populated

Field

Type

Populated

fileSize

Long

Yes

location

String [255]

Yes. location of the file in S3 e.g: http://127.0.0.1:9000/miniodatafiles/2812a823d155cca47e47af37201c7e2c

But needs updating once files are transferred to tape

checksum

String [255]

No

name

String [255] NOT NULL

Yes

createId

String

Yes (auto; simple/root)

doi

String [255]

No

createTime

Date

Yes (auto)

modTime

Date

Yes (auto)

datafileModTime

Date

Yes

modId

String

Yes (auto)

datafileCreateTime

Date

Yes, but set to be the same value as datafileModTime

description

String [255]

Yes, hardcoded to User uploaded file