Entry Types
someplugin exampletypes.xml htdocs myplugin example.pngFor example, this would allow you to reference the example.png image as an icon for the entry type with the property:
<property name="icon" value="/myplugin/example.png"/>>There are many many plugins defined in the RAMADDA source that have types.xml file that can be used as reference: https://github.com/geodesystems/ramadda/tree/master/src/org/ramadda/plugins and https://github.com/geodesystems/ramadda/tree/master/src/org/ramadda/geodata
Column Data Types
- string - Use size="..." to specify the column size
- enumeration - See below to specify values
- enumerationplus - Just like enumeration but allows use to enter new text values
- list - A big string internally but shows a list of newline separated text values to the user
- password - A string but is shown in a password field and is not exported or otherwise accessible.
- int - Integer
- double - floating point number
- percentage - floating point number shows as percentage
- boolean - true of false
- date - A date
- datetime - A date and a time
- clob - A big character large object
- email - Shows as an email address
- url - Shows as a URL
- latlon - A single geographic point
- latlonbbox - Geographic spatial bounds
<column name="fruit" label="Fruit" type="enumeration" values="apple,banana,orange" cansearch="true" />If this is a large list you can define the values in an external file. This file can be contained in a plugin .zip file or can be stored in your RAMADDA home directory under a "resources" subdirectory. The rule is that the file path has to have a "resources" directory in it. For example, in the Archive plugin there is a resources directory under the full path: values="file:/org/ramadda/plugins/archive/resources/lithology.txt"
Wiki Template
<wiki> <![CDATA[ +section title={{name}} :navtop { {description wikify=true}} :heading Charts { {group}} { {display type=linechart showMenu=true fields=discharge}} { {display type=linechart showMenu=true fields=gauge_height}} :vspace 0.5em :heading Table { {display_download}} { {display_table}} :vspace 1em ---- :heading Information +row +col-md-6 { {information details="true" showTitle="false" }} -col +col-6 { {map}} -col -row -section ]]> </wiki>
Create Entry Type Form
Entry Type - Basic
- A type ID - this needs to start with type_, be lower case with no spaces or special characters. If there are columns defined then this will also be the database table name.
- A human readable name for the type
- A "super type" - entry types in RAMADDA are hierarchical. So for example, in the Archive plugin we have a Site Collection type that has geographic metadata. Other types in that plugin (e.g, Geologic Specimen) have the Site Collection as their super type, thus inheriting the geographic metadta. If you want this to be point data (e.g., CSV files) then specify type_point (e.g., CSV files). There is a link to the master list of all entry types available.
- Java handler - this is the Java class that handles this type. RAMADDA will try to figure out what this value should be but you can set it explicitly. If this is point data (e.g,CSV files) then specify "PointTypeHandler". If it is just some normal entry but you will specify metadata columns then specify "GenericTypeHandler". Else leave is as Default.
- You can specify an optional Super Category and Category. This is used to organize the big list of types.
- An icon. You can provide your own icon as described above or view the icons available at /repository//icons.html
Entry Type - Properties
attribute_name="value"
Entry Type - Advanced Configuration
Entry Type - Columns
Entry Type - Admin
<types> <import resource="type_archive_site.xml"/> <import resource="type_archive_specimen.xml"/> </types>If the "Yes, drop the database table" is checked and your password is entered then the whole database table is dropped and recreated from the Columns definiton. Be careful using this as any data might be lost. This is provided because sometimes the database data type of column definitions has to be changed (e.g, a string to a double) and the change isn't allowed by the database.
Creating the entry type
CITATION REQUEST: When using model or observational data obtained
through FACTS in a publication, please provide a citation
in the paper to the original underlying data source. This includes both
downloading data and creating analysis figures through FACTS.
A list of original sources for citation is here.