metamod:user_database_revised

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
metamod:user_database_revised [2010-09-24 12:48:11]
egils 		metamod:user_database_revised [2022-05-31 09:29:32] (current)
Line 7: Line 7:
  
 **2010-09-24: Changes in the database structure. A row in the File table is now directly owned by a user. These changes are rendered in bold.** **2010-09-24: Changes in the database structure. A row in the File table is now directly owned by a user. These changes are rendered in bold.**
 +
 +**2010-09-28: Added the file_delete method.**
 +
 +2010-11-11: Removed WMS_URL and WMS_XML entries from the InfoDS table
  
 ===== Overview ===== ===== Overview =====
Line 86: Line 90:
 ^LOCATION |Location. Single entity. Absolute path to the directory under which all files belonging to the dataset are found. The files may be found directly in the location directory, or in any subdirectory of the location directory at any level. | ^LOCATION |Location. Single entity. Absolute path to the directory under which all files belonging to the dataset are found. The files may be found directly in the location directory, or in any subdirectory of the location directory at any level. |
 ^CATALOG |Partial URL to a THREDDS dataset. Single entity. Combined with the file name, this URL can be used to access the content of a file through a TDS server. It can also provide the URL that points to the THREDDS catalog containing the METAMOD dataset. | ^CATALOG |Partial URL to a THREDDS dataset. Single entity. Combined with the file name, this URL can be used to access the content of a file through a TDS server. It can also provide the URL that points to the THREDDS catalog containing the METAMOD dataset. |
-^WMS_URL |URL to the WMS service that can display data from the dataset. Single entity. | 
-^WMS_XML |XML document that describes available alternatives for displaying the dataset in WMS. For example, the parameters that can be displayed. Each parameter may have a palette (for example "BOXFILL/redblue") found in a style element in the GetCapabilites document. If no palette is found, a default palette is used for the parameter. | 
 |Additional information types may be added later, for example to implement projection information: || |Additional information types may be added later, for example to implement projection information: ||
 ^PROJECTION_XML |XML document used to represent reprojection information. The document contains, among other things, each projection the user has asked for ("Lat/Long", "Stereo" etc.). Each projection contains attributes: method, projString, xAxis, yAxis and toDegree.  | ^PROJECTION_XML |XML document used to represent reprojection information. The document contains, among other things, each projection the user has asked for ("Lat/Long", "Stereo" etc.). Each projection contains attributes: method, projString, xAxis, yAxis and toDegree.  |
Line 183: Line 185:
 |file_first |Make the first file (**owned by the current user**) the current file. |OUT: true if found, false if no files exist. | |file_first |Make the first file (**owned by the current user**) the current file. |OUT: true if found, false if no files exist. |
 |file_next |Make the next file in the database the current one. |OUT: true if found, false if already last file. | |file_next |Make the next file in the database the current one. |OUT: true if found, false if already last file. |
 +|**file_delete** |**Delete the current file entry from the database.** |**OUT: true if the entry was deleted, false on error.** |
  
 ==== Example usecase ==== ==== Example usecase ====
  • metamod/user_database_revised.1285332491.txt.gz
  • Last modified: 2022-05-31 09:23:19
  • (external edit)