annotate base/database/classes.lisp @ 288:d1e5bbcc5ea4
Rationalise base and geerdes classes, constructors and methods.
Ignore-this: d9d4d88566a6d110844d91d4c70513cd
Towards a more standardised interface. Some of these changes (generalised
constructors and reader functions) are necessary for amuse-database-admin
functionality and some other CHARM-like things.
darcs-hash:20090716154406-16a00-8a9b4fb1fc1f5ba75af66a1bbd87e1bb68e02493.gz
| author |
j.forth <j.forth@gold.ac.uk> |
| date |
Thu, 16 Jul 2009 16:44:06 +0100 |
| parents |
00d35eb70ef9 |
| children |
|
| rev |
line source |
|
j@287
|
1 (cl:in-package #:amuse-database-admin)
|
|
j@287
|
2
|
|
j@287
|
3 (defclass amuse-dataset-identifier (identifier)
|
|
j@287
|
4 ((dataset-id :reader dataset-id
|
|
j@287
|
5 :initarg :dataset-id))
|
|
j@287
|
6 (:documentation "A dataset is a set of pieces used for a particualar
|
|
j@287
|
7 analytical task. A dataset is not necessarily the same thing as a
|
|
j@287
|
8 corpus or collection (are these things different?). Corpus indicates
|
|
j@287
|
9 that a set of pieces have been curated in some way and in that sense
|
|
j@287
|
10 `belong together'. A dataset is just simply a set of pieces gathered
|
|
j@287
|
11 together to analyse, and the pieces can be from any corpus or
|
|
j@287
|
12 backend (hence the amuse- prefix"))
|
|
j@287
|
13
|
|
j@287
|
14 (defclass amuse-dataset (list-slot-sequence)
|
|
j@287
|
15 ((identifier :initarg :identifier
|
|
j@287
|
16 :reader identifier)
|
|
j@287
|
17 (description :initarg :description
|
|
j@287
|
18 :reader description)))
|
