source: MILK/trunk/milk_server/milk_server/templates/atom_editor/atom_help.html @ 4735

Subversion URL:
Revision 4735, 52.1 KB checked in by cbyrom, 12 years ago (diff)

Add link and anchor to curating data help section.

1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "">
2<html xmlns=""
3        xmlns:py="" 
4        xmlns:xi="">
5        <xi:include href="layout.html" />
6        <xi:include href="atom_functions.html" />
7        <head>
8        <title py:content="c.title">title</title>
9    </head>
10  <body class="submit">
11      <panelTab>Editor</panelTab>
12        <div id="contents">
13            <div class="metadata">
14                            <h3>  $c.title
15                    </h3>
16                                <h2>Contents</h2>
17                                <div class="headingblock">                 
18                    <ol>
19                        <li><a href="#intro">Introduction</a></li>
20                        <li><a href="#home">Editor home page</a></li>
21                        <li><a href="#creating">Creating an atom</a></li>
22                        <li><a href="#searching">Searching atoms</a></li>
23                        <li><a href="#editing">Editing an atom</a></li>
24                        <li><a href="#granulite">Importing granulite data</a></li>
25                        <li><a href="#csml">Importing CSML/CDML data</a></li>
26                        <li><a href="#deleting">Deleting granule atoms</a></li>
27                        <li><a href="#structure">Appendix A: Atom XML structure</a></li>
28                        <li><a href="#example">Appendix B: Creating an example set of metadata documents</a></li>
29                        <li><a href="#exampleCurating">Appendix C: Curating an example set of metadata documents</a></li>
30                    </ol>
31                    </div>
32                    <a name="intro"><h2>Introduction</h2></a>
33                                <div class="headingblock">                 
34                    <p>
35                    This editor allows the creation and maintenance of metadata documents in the MOLES2.0
36                    (Metadata Objects for Links in Environmental Science) format - which is based on the Atom
37                    Syndication Format v1.0 (details
38                    <a href="">here</a>).  It
39                    replaces the CEDAR editor which produced documents according to the more complex, MOLES1.3 schema.  NB,
40                    documents produced using this older schema should be available in the BADC system in new format; if not,
41                    a migration script exists with which to enable this - contact the system administrator for details**.
42                    </p>
43                    <p>
44                    Full details of the MOLES2.0 schema are provided in section, '<a href="#structure">Appendix A: Atom XML structure</a>'.
45                    </p>
46                                </div>
47                    <a name="home"><h2>Editor home page</h2></a>
48                                <div class="headingblock">                 
49                    <p>
50                    The editor home page is available <a href="${h.url_for('atomHome')}">
51                    here</a>.  The following options are available:
52                    <ul>
53                    <li>
54                            <a href="${h.url_for('create')}">Create atom</a>
55                            - see section, '<a href="#creating">Creating an atom</a>'
56                    </li>
57                    <li>
58                            <a href="${h.url_for('createGranule')}">Create data granule atom using granulite file</a>
59                            - see section, '<a href="#granulite">Importing granulite data</a>'
60                    </li>
61                    <li>
62                            <a href="${h.url_for('list')}">Edit/List atoms</a>
63                            - see sections, '<a href="#editing">Editing an atom</a>' and '<a href="#searching">Searching atoms</a>'
64                    </li>
65                    <li>
66                            <a href="${h.url_for('help')}">Help</a>
67                            - display this page
68                    </li>
69                    </ul>
70                    </p>
71                    </div>
73                    <a name="creating"><h2>Creating an atom</h2></a>
74                                <div class="headingblock">                 
75                    <p>
76                    Atom metadata documents are created in two stages - firstly specifying the essential, 'header' information
77                    then filling out the remaining detail.  Documents are created by visiting the,
78                    '<a href="${h.url_for(controller='atom_editor/editatom',action='create')}">Create atom</a>' page.  This
79                    presents the user with four input fields that MUST be specified in order for the document to be created:
80                    <dl>
81                    <dt><b>Provider ID</b></dt>
82                    <dd>
83                    the name of the organisation providing the data - selectable from a pre-specified drop down list
84                    </dd>
85                    <dt><b>Data Type</b></dt>
86                    <dd>
87                    the type of atom document to produce.  This relates to the type of underlying data that
88                    the metadata is describing and must be set to one of the following, pre-specified values:
89                        <dl>
90                        <dt><b>Data Entity</b></dt>
91                        <dd>
92                        a general, high level metadata document allowing the grouping of data granules
93                        and deployments data together in a logical manner - e.g. bringing together a data granule describing a
94                        particular data file with the observation stations, data production tools and activities involved in creating it.
95                        </dd>
96                        <dt><b>Data Granule</b></dt>
97                        <dd>
98                        acts as a 'wrapper' to specific data files, providing summary metadata in
99                        order to aid discovery.  NB, data granules can be created or augmented by ingesting data directly into
100                        the system - see sections, '<a href="#importing">Importing granulite data</a>' and '<a href="#csml">Importing CSML/CDML data</a>'
101                        </dd>
102                        <dt><b>Activity</b></dt>
103                        <dd>
104                        a metadata document describing an activity used to create a dataset.
105                        </dd>
106                        <dt><b>Data Production Tool (DPT)</b></dt>
107                        <dd>
108                        a metadata document describing an instrument involved in the creation of a dataset.
109                        </dd>
110                        <dt><b>Observation Station</b></dt>
111                        <dd>
112                        a metadata document describing the observation station used to create a dataset.
113                        </dd>
114                        <dt><b>Deployment</b></dt>
115                        <dd>
116                        a simple metadata document allowing the grouping of Activity, Data Production Tool and Observation
117                        Station documents in a logical manner - i.e. to pull together the why/how/where of data production.  NB, any number of
118                        activities, data production tools and observation stations can be specified in a single deployment and these will all
119                        share the same temporal and spatial coverage summary information.  Also note, data entities do not specify references to
120                        activities, DPTs or observation stations metadata document directly; rather they reference Deployment documents which, in turn, reference
121                        these documents.  Note, a Deployment atom is just a specialisation of the 'Activity' atom type - but with a subtype of, 'Deployment'.
122                        </dd>
123                        </dl>
124                    </dd>
125                    <dt><b>Title</b></dt>
126                    <dd>
127                    free text field to specify a title for the metadata document
128                    </dd>
129                    <dt><b>Author</b></dt>
130                    <dd>
131                    free text field to specify the principal author of the underlying data described by the metadata document.
132                    </dd>
133                    </dl>
134                    Note, the atom types, 'Actitivity', 'Observation Station' and 'Data Production Tool' are known collectively as
135                    <em>Deployments data</em> - and this should not be confused with the 'Deployment' atom type - which is the document
136                    type which groups together Deployments data.
137                    </p>
138                    <p>
139                    Once the header info is completed, the atom document is created and the user is taken to the 'Edit' page
140                    (see section, '<a href="#editing">Editing an atom</a>') where additional content can be specified.  Note, the edit
141                    page allows the author and title details to be edited, however the provider and type data cannot be changed
142                    following document creation.
143                    </p>
144                    </div>
146                    <a name="searching"><h2>Searching atoms</h2></a>
147                                <div class="headingblock">                 
148                    <p>
149                    The atom metadata catalogue can be searched by visiting the
150                    '<a href="${h.url_for(controller='atom_editor/listatom',action='list', searchData=None)}">Edit/List atoms</a>' page.
151                    This provides a simple search filter allowing the user to specify the following inputs to search on:
152                    <dl>
153                    <dt><b>Provider ID</b></dt><dd>
154                    - the name of the organisation providing the data - selectable from a pre-specified drop down list
155                    </dd>
156                    <dt><b>Data Type</b></dt>
157                    <dd>
158                    the type of atom document to search for - selectable from a pre-specified drop down list
159                                </dd>
160                                <dt><b>Search Text</b></dt>
161                                <dd>
162                                a free text field to allow searching for specific data
163                                </dd>
164                                </dl>
165                                NB, the 'Search Text' field allows the contents of the atom elements to be searched and is done in a
166                                cumulative manner when multiple words are specified - e.g. searching using, 'temperature hot' will return
167                                all atoms which feature both the words 'temperature' and 'hot', although not necessarily in that order or
168                                adjacent to one another.  Additionally, simple wildcards can be used in the searches - using '*' to represent
169                                all characters, multiple times and '?' to represent a single character - demonstrated as follows:
170                                <dl>
171                                        <dt><b>temp*</b></dt>
172                                        <dd>
173                                        will return existing documents containing 'temperature', 'temperate', 'temporary', etc
174                                        </dd>
175                                        <dt><b>?eather</b></dt>
176                                        <dd>
177                                        will return existing documents containing 'weather', 'heather', 'leather', etc
178                                        </dd>
179                                </dl>
180                                Note, also, text searches are case insensitive.
181                                </p>
182                                <p>
183                                To search for documents, enter the required search terms (NB, leaving the filter in its initial state, with
184                                Provider ID and Data Type set to 'All' and Search Text empty, will return all available atom documents) and
185                                click the 'Search' button.  If data exists matching the search criteria, these will be displayed after a short
186                                pause in a table of results.  To view this data in more detail, click the 'Edit' button associated with it.  This will
187                                take you to the atom editor, described in the section, '<a href="#editing">Editing an atom</a>'.
188                    </p>
189                    </div>
191                    <a name="editing"><h2>Editing an atom</h2></a>
192                                <div class="headingblock">                 
193                    <p>
194                    The main 'Edit' page for an atom is reached via two routes: either by creating a new atom
195                    (see section, '<a href="#creating">Creating an atom</a>'); or by searching
196                    existing atoms and electing to edit one of these (see section, '<a href="#searching">Searching atoms</a>').
197                    </p>
198                    <p>
199                    The following inputs are available to the atom editor - note, some are
200                    only available to specific atom types:
201                    <dl>
202                    <dt><b>Title</b>
203                    </dt>
204                    <dd>
205                    free text field to specify a title for the metadata document
206                    </dd>
207                    <dt>
208                    <b>Sub-Type</b> (not Deployments or Granules)
209                    </dt>
210                    <dd>
211                    more specific classification of the type of the underlying data - selectable from a fixed list - which is dependent on the main atom type
212                    </dd>
213                    <dt>
214                    <b>Abbreviation</b> (not Deployments or Granules)
215                    </dt>
216                    <dd>
217                    free text field to specify an abbreviation for the data
218                    </dd>
219                    <dt>
220                    <b>Upload data</b> (Data Granules only)
221                    </dt>
222                    <dd>
223                                functionality to allow the import of data direct from CDML or CSML
224                                files - as described in section, '<a href="#csml">Importing CSML/CDML data</a>'.
225                    </dd>
226                    <dt>
227                    <b>Summary</b> (not Deployments or Granules)
228                    </dt>
229                    <dd>
230                    free text area to provide an abstract for the data
231                    </dd>
232                    <dt>
233                    <b>Content</b> (not Deployments)
234                    </dt>
235                    <dd>
236                    the actual main content of the metadata document.  This may just be
237                    text content, but in the case of Granule atoms, if a CSML or CDML file
238                    has been specified (see section '<a href="#csml">Importing CSML/CDML data</a>',
239                    this will be set as the atom content.
240                    </dd>
241                    <dt>
242                    <b>Author</b>
243                    </dt>
244                    <dd>
245                    the principal author of the underlying data being described by the atom. An
246                    email address can be provided with the author name.
247                    </dd>
248                    <dt>
249                    <b>Contributors</b> (not Deployments)
250                    </dt>
251                    <dd>
252                    secondary authors of the underlying data - together with email addresses, if required.
253                    Three contributors can be added at a time; if more are required, add the first three
254                    then click, 'Update' - and space will be added to input another three contributors.
255                    Contributors can be removed by selecting the check box and clicking on 'Remove'.  NB,
256                    multiple contributors can be removed at once.
257                    </dd>
258                    <dt>
259                    <b>Online References</b> (not Deployments or Granules)
260                    </dt>
261                    <dd>
262                    reference links to data associated with the underlying data - composed of a link 'type',
263                    or 'relation' together with a URI and a title.  Note, the URI must follow the format,
264                    '' - i.e. including the full address.  Like 'Contributors', it is
265                    possible to add and remove multiple online references at once.
266                    </dd>
267                    <dt>
268                    <b>Associated Data Granules</b> (Data Entities only)
269                    </dt>
270                    <dd>
271                    references to existing data granule atoms.  Clicking
272                    on the 'Add' link in this section takes the user to the atom list page (see section
273                    '<a href="#searching">Searching atoms</a>').  Since the user is setting up
274                    data granule associations, only atoms of this type can now be searched on.  Once
275                    a search has been done (narrowing results by specifying suitable search terms, if required),
276                    if results have been found, the user can then set up associations with these, by
277                    using the checkboxes to select the specific granules and then clicking 'Add selections'.
278                    If associations with granules need to be removed, click the 'Edit' link, select the
279                    granule(s) to remove using the checkbox and then click, 'Remove'.
280                    </dd>
281                    <dt>
282                    <b>Associated Deployments</b> (Data Entities only)
283                    </dt>
284                    <dd>
285                    references to existing deployment atoms.  The process to add
286                    and remove associations is the same as for data granules, above.
287                    </dd>
288                    <dt>
289                    <b>Associated Data</b> (Deployments only)
290                    </dt>
291                    <dd>
292                    references to existing activity/observation station/data production tool atoms.  The process to add
293                    and remove associations is the same as for data granules, above.
294                    </dd>
295                    <dt>
296                    <b>Parameters</b> (Data Entities only)
297                    </dt>
298                    <dd>
299                    parameters categorising the underlying data described by the metadata document.  Parameter data consists
300                    of a label together with a URL to a valid vocabulary term (i.e. available from a vocab server - such as
301                    '') and term ID.  On input the validity of the vocab term data is checked and
302                    the data will be rejected if it is invalid.
303                    </dd>
304                    <dt>
305                    <b>Data Coverage</b>
306                    </dt>
307                    <dd>
308                    a summary of the spatiotemporal coverage of the underlying data.  Input fields allow the specification of
309                    max/min coordinates and temporal ranges.
310                    </dd>
311                    <dt>
312                    <b>Responsible Parties</b>
313                    </dt>
314                    <dd>
315                    information on individuals responsible for the creation and maintenance
316                    of the actual atom metadata document - consists of free text information
317                    to specify the user role, name and uri (if required).  As with Contributors,
318                    multiple data can be added - and subsequently removed.
319                    </dd>
321                    </dl>
323                    In addition to the input fields, some atom types have additonal, 'summary'
324                    information displayed - relating to atoms which have a logical reference to
325                    the current document.  Specifically, the following summaries are available:
326                    <dl>
327                    <dt>
328                    <b>Associated Deployments Data (summary/details)</b> (Data Entities and Deployments data only)
329                    </dt>
330                    <dd>
331                    displays a list of the associated Deployments data - via associated Deployment atoms - i.e.
332                    this gathers info from all Deployment documents which reference the current
333                    data and lists out all the other Deployments data featured.  For example, if a Deployment
334                    features Activity1, DPT1 and Observation Station2, and we are viewing Activity1, then
335                    DPT1 and Observation Station2 will be displayed (together with links to the actual docs)
336                    here.  Clicking on the plus/minus sign toggles between the summary and details mode.
337                    Summary mode displays a unique list of the associated Deployments data whereas details mode
338                    shows exactly how this is grouped, together with temporal ranges, in the Deployment atoms.
339                    </dd>
340                    <dt>
341                    <b>Associated Data Entities - summary</b> (Deployments data and Granules only)
342                    </dt>
343                    <dd>
344                    displays a list of the associated Data Entities data - together with links to this data. 
345                    For Deployments data, the list is constructed
346                    by finding all Deployment atoms which feature the currently displayed atom, then
347                    finding all Data Entities which reference these Deployments.  For Data Granule atoms,
348                    this list is constructed by finding all the Data Entities which directly reference the
349                    displayed Granule.
350                    </dd>
351                    </dl>
352                    </p>
353                    </div>
354                    <a name="granulite"><h2>Importing granulite data</h2></a>
355                                <div class="headingblock">                 
356                    <p>
357                    Data can be imported directly into the system using a type of data file known
358                    as a <em>granulite</em>.  These are used to create Data Granule metadata documents
359                    and set up associations with existing Data Entities.  The format of a granulite file
360                    can be seen here - <a href="${h.url_for('example')}">example granulite</a>.
361                    </p>
362                    <p>
363                    When a valid granulite file has been constructed, the contents may be ingested by
364                    visiting the '<a href="${h.url_for('createGranule')}">Create data granule atom using granulite file</a>' page.
365                    This presents the user with the following input fields:
366                    <dl>
367                    <dt><b>
368                    Granulite File
369                    </b></dt>
370                    <dd>
371                    Clicking on 'Browse...' produces a file browser window to allow users to
372                    navigate and select their granulite file.
373                    </dd>
374                    <dt><b>
375                    CSML or CDML file
376                    </b></dt>
377                    <dd>
378                    Clicking on 'Browse...' produces a file browser window to allow users to
379                    navigate and select their CSML or CDML file.  This file is used to augment data
380                    specified in the granulite file and is uploaded to the document repository upon
381                    ingest.  Note, only one CSML or CDML
382                    file can be ingested per granulite file.  Also note, if a CDML file is ingested
383                    it is coverted into a CSML file, as part of the ingest, to extract the required
384                    summary data; both the original CDML file and the generated CSML file are subsequently
385                    stored in the document repository.
386                    </dd>
387                    <dt><b>
388                    Dataset ID
389                    </b></dt>
390                    <dd>
391                    *****************THIS SHOULD PROBABLY BE REMOVED - NEEDS TESTING....****
392                    </dd>
393                    <dt><b>
394                    Time axis
395                    </b></dt>
396                    <dd>
397                    If a CDML file is specified, it is necessary to identify the time axis label
398                    used by the file in order to extract all the available data.  If no axis is provided,
399                    the default, 'time' will be used.
400                    </dd>
401                    </dl>
402                    </p>
403                    <p>
404                    <h2>Use Cases</h2>
405                    The ingesting of granulite data has several possible workflows; these are
406                    described in detail here.
407                    <dl>
408                    <dt><b>
409                    1. Ingest of new granulite, with no CSML/CDML file, describing new Data Granule
410                    </b></dt>
411                    <dd>
412                    The granulite should not have a dataset_id specified in the granule_info as this
413                    will be automatically generated upon ingest.  User selects the granulite file
414                    using the 'Granulite file' Browse input.  User clicks 'Upload'.  The data is then
415                    ingested and, if no problems are encountered, a new Data Granule is created using
416                    this data and then displayed.
417                    </dd>
418                    <dt><b>
419                    2. Ingest of old granulite, with no CSML/CDML file or dataset_id specified
420                    </b></dt>
421                    <dd>
422                    If no dataset_id has been specified, the ingest process has no way of knowing
423                    that the data has already been ingested.  In this case, a new Data Granule is
424                    created - effectively with identical contents to another Data Granule.
425                    </dd>
426                    <dt><b>
427                    3. Ingest of old granulite, with no CSML/CDML file specified, but dataset_id of existing Data Granule <em>is</em>specified
428                    </b></dt>
429                    <dd>
430                    If the dataset_id has been specified, and if an existing Data Granule is already using this ID, the
431                    ingest process is interupted and the user is asked whether they want to overwrite the existing
432                    Data Granule with the new Data Granule generated from the granulite file contents.  If the user
433                    clicks, 'Cancel' then the ingest is halted and they remain on the granulite ingest page.  If they
434                    click, 'Ok' then the ingest continues and the old Data Granule is replaced with the new one.  NB, in
435                    this scenario, any links between Data Entities and the old Data Granule are removed.
436                    </dd>
437                    <dt><b>
438                    4. Ingest of new granulite with CSML file specified
439                    </b></dt>
440                    <dd>
441                    Work flow as Use Case 1, however a CSML file is also specified - using the Browse input for this
442                    field.  When the user clicks 'Upload' the CSML file is the scanned to extract the following data:
443                    <ul>
444                    <li>
445                    CSML ID - to be used as the produced Data Granule dataset ID
446                    </li>
447                    <li>
448                    Title
449                    </li>
450                    <li>
451                    Spatiotemporal coverage data
452                    </li>
453                    <li>
454                    Parameters data
455                    </li>
456                    </ul>
457                    This is used to create a new Data Granule and the CSML file is uploaded to the
458                    document repository.  The granulite data is then extracted
459                    and applied to this new Data Granule.  NB, this will lead to replacement of any
460                    single value data, if specified - i.e. the ID, Title and coverage data.  The parameters
461                    data will be augmented with any new, unique terms.
462                    </dd>                   
463                    <dt><b>
464                    5. Ingest of new granulite with CDML file specified
465                    </b></dt>
466                    <dd>
467                    As Use Case 4, however the CDML file is firstly converted into a
468                    CSML file, using the additional supplied inputs, if required.  NB, both
469                    the original CDML file and the generated CSML file are uploaded to the
470                    document repository.
471                    </dd>
472                    <dt><b>
473                    6. Ingest of old granulite with CSML/CDML file and dataset ID specified
474                    </b></dt>
475                    <dd>
476                    Similarly to Use Case 3, the user will be prompted to confirm whether the
477                    ingest should complete - and overwrite the existing Data Granule.  If the
478                    user selects to do this, workflow continues as for Use Case 4/5.
479                    </dd>
480                    </dl>
481                    </p>
482                    <p>
483                    Note, the granulite ingest functionality is also available as a command line
484                    process - which may be more appropriate for batch processing large numbers of
485                    granulite files.
486                    </p>
487                    </div>
488                    <a name="csml"><h2>Importing CSML/CDML data</h2></a>
489                                <div class="headingblock">                 
490                    <p>
491                    As well as importing data from granulite files (see section, '<a href="#granulite">Importing granulite data</a>'),
492                    it is also possible to ingest data directly from CSML or CDML files into existing Data Granules.
493                    </p>
494                    <p>
495                    If a Data Granule doesn't already have a CSML or CDML file associated with it, it
496                    will have an 'Upload data' input section available to it in edit mode.  This is
497                    similar to the input used for the granulite ingest - except the option to specify
498                    a granulite file is absent.  A user can specify a CSML or CDML file and click,
499                    'Upload' to add data from the file to the Data Granule.  NB, as with the granulite
500                    ingest, if a CDML file is specified, it may be necessary to include a time axis, to
501                    aid the parsing of this file.  Also, like the granulite ingest, CDML files are used
502                    to create CSML files - and both these types of document are uploaded to the document
503                    repository as part of the upload process.
504                    </p>
505                    <p>
506                    When the upload is completed, the new data is saved to the Data Granule and this is
507                    reloaded to display the new contents.  NB, it is only possible to associate a single
508                    CDML or CSML file with a Data Granule so, following the initial upload, this input
509                    functionality is then disabled.  The 'Content File' section is filled in automatically
510                    to display the name of the uploaded CSML/CDML.
511                    </p>
512                    </div>
513                    <a name="deleting"><h2>Deleting granule atoms</h2></a>
514                                <div class="headingblock">                 
515                    <p>
516                    Data Granules, and their associations with Data Entities, may be deleted from
517                    the system.  To do this, access the Data Granule in question, via the search
518                    page (see section '<a href="#searching">Searching atoms</a>') and click on the
519                    'Delete' button at the top of the editor.  The user is then presented with a
520                    confirmation dialog, to avoid accidental deletion of data.  If the user confirms the
521                    delete, the Data Granule atom is deleted and links to it from Data Entity atoms are removed.
522                    NB, before the atom is deleted a copy is stored in the backup collection of the document
523                    repository.
524                    </p>
525                    </div>
526                    <a name="structure"><h2>Appendix A: atom XML structure</h2></a>
527                                <div class="headingblock">                 
528                    <p>
529                    The XML structure of a dummy Data Entity document is given described below.  The various metadata inputs
530                    discussed in section, '<a href="#editing">Editing an atom</a>' should be evident in this structure.  Points of note
531                    include:
532                    <ul>
533                    <li>
534                    Online references are stored as atom links
535                    </li>
536                    <li>
537                    Parameters are stored as atom categories
538                    </li>
539                    <li>
540                    Atom type and subtype are stored as atom categories
541                    </li>
542                    <li>
543                    The atom id element is a unique identifier - an IRI as specified by <a href="">[RFC3987]</a> - this includes the atom dataset ID
544                    </li>
545                    <li>
546                    The Atom1.0 schema has been extended to include data that didn't naturally fit in it, namely:
547                        <ul>
548                        <li>
549                                Spatiotemporal data - which is described in GEOSS, GML and Moles elements
550                        </li>
551                        <li>
552                        Responsible parties data
553                        </li>
554                        <li>
555                        Dataset and metadata language
556                        </li>
557                        <li>
558                        Abbreviation
559                        </li>
560                        <li>
561                        Creation date
562                        </li>
563                        <li>
564                        Provider ID
565                        </li>
566                        </ul>
567                        NB, the Moles elements are based on the old MOLES1.3 format.  Note, also, that the schema
568                        could be further simplified by judicious use of vocab terms - effectively translating
569                        the latter four bits of data into categories data.
570                    </li>
571                    </ul>
572                    <pre>
573            <div class="xmlDocBig"><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">entry <span class="xmlAttrTyp">xmlns</span>="<span class="xmlAttrVal"></span>" <span class="xmlAttrTyp">xmlns:georss</span>="<span class="xmlAttrVal"></span>"
574            <span class="xmlAttrTyp">xmlns:moles</span>="<span class="xmlAttrVal"></span>" <span class="xmlAttrTyp">xmlns:gml</span>="<span class="xmlAttrVal"></span>"</span><b>></b>
575<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">id</span><b>></b>tag:localhost,2008-12-23:/view/<b>&lt;</b>/<span class="xmlElemTag">id</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">title</span><b>></b>A data entity describing some data used in a measurement.<b>&lt;</b>/<span class="xmlElemTag">title</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">link</span> <span class="xmlAttrTyp">href</span>="<span class="xmlAttrVal">http://localhost:5000/view/</span>" <span class="xmlAttrTyp">rel</span>="<span class="xmlAttrVal">self</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">link</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">link</span> <span class="xmlAttrTyp">href</span>="<span class="xmlAttrVal">http://localhost:5000/view/</span>"
576<span class="xmlAttrTyp">rel</span>="<span class="xmlAttrVal">NOT YET SET UP/None/Deployment</span>" <span class="xmlAttrTyp">title</span>="<span class="xmlAttrVal">dep1</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">link</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">link</span> <span class="xmlAttrTyp">href</span>="<span class="xmlAttrVal">http://localhost:5000/view/</span>"
577<span class="xmlAttrTyp">rel</span>="<span class="xmlAttrVal">NOT YET SET UP/None/Deployment</span>" <span class="xmlAttrTyp">title</span>="<span class="xmlAttrVal">dep266</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">link</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">link</span> <span class="xmlAttrTyp">href</span>="<span class="xmlAttrVal">http://localhost:5000/view/</span>"
578<span class="xmlAttrTyp">rel</span>="<span class="xmlAttrVal">GRAN - NOT YET SET UP/None/GRANULE</span>" <span class="xmlAttrTyp">title</span>="<span class="xmlAttrVal">gran1</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">link</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">link</span> <span class="xmlAttrTyp">href</span>="<span class="xmlAttrVal">http://localhost:5000/view/</span>"
579<span class="xmlAttrTyp">rel</span>="<span class="xmlAttrVal">GRAN - NOT YET SET UP/None/GRANULE</span>" <span class="xmlAttrTyp">title</span>="<span class="xmlAttrVal">new gran12</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">link</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">link</span> <span class="xmlAttrTyp">href</span>="<span class="xmlAttrVal"></span>" <span class="xmlAttrTyp">rel</span>="<span class="xmlAttrVal"></span>" <span class="xmlAttrTyp">title</span>="<span class="xmlAttrVal">Tessella</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">link</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">link</span> <span class="xmlAttrTyp">href</span>="<span class="xmlAttrVal"></span>" <span class="xmlAttrTyp">rel</span>="<span class="xmlAttrVal"></span>" <span class="xmlAttrTyp">title</span>="<span class="xmlAttrVal">Data</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">link</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">link</span> <span class="xmlAttrTyp">href</span>="<span class="xmlAttrVal"></span>" <span class="xmlAttrTyp">rel</span>="<span class="xmlAttrVal"></span>" <span class="xmlAttrTyp">title</span>="<span class="xmlAttrVal">object home</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">link</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">author</span><b>></b>
580<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">name</span><b>></b>Mr Smith<b>&lt;</b>/<span class="xmlElemTag">name</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">email</span><b>></b><b>&lt;</b>/<span class="xmlElemTag">email</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">author</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">contributor</span><b>></b>
581<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">name</span><b>></b>Mrs Smith<b>&lt;</b>/<span class="xmlElemTag">name</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">email</span><b>></b><b>&lt;</b>/<span class="xmlElemTag">email</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">contributor</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">contributor</span><b>></b>
582<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">name</span><b>></b>Mr Yang<b>&lt;</b>/<span class="xmlElemTag">name</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">email</span><b>></b><b>&lt;</b>/<span class="xmlElemTag">email</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">contributor</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">category</span> <span class="xmlAttrTyp">term</span>="<span class="xmlAttrVal">ATOM_TYPE</span>" <span class="xmlAttrTyp">scheme</span>="<span class="xmlAttrVal">DE - NOT YET SET UP/None/DE</span>" <span class="xmlAttrTyp">label</span>="<span class="xmlAttrVal">DE</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">category</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">category</span> <span class="xmlAttrTyp">term</span>="<span class="xmlAttrVal">ATOM_SUBTYPE</span>" <span class="xmlAttrTyp">scheme</span>="<span class="xmlAttrVal">NOT YET SET UP/None/dgMeasurement</span>" <span class="xmlAttrTyp">label</span>="<span class="xmlAttrVal">dgMeasurement</span>"<b>></b><b>&lt;</b>/<span class="xmlElemTag">category</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">summary</span><b>></b>This data entity represents some measurement data.<b>&lt;</b>/<span class="xmlElemTag">summary</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">content</span> <span class="xmlAttrTyp">type</span>="<span class="xmlAttrVal">xhtml</span>"<b>></b>
583<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">{}div</span><b>></b>Some more details of the measurement data.
586blah...<b>&lt;</b>/<span class="xmlElemTag">{}div</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">content</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">updated</span><b>></b>2008-12-24T13:42:51Z<b>&lt;</b>/<span class="xmlElemTag">updated</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">published</span><b>></b>2008-12-23T13:45:59Z<b>&lt;</b>/<span class="xmlElemTag">published</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:entity</span><b>></b>
587<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:molesISO</span><b>></b>
588<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:datasetLanguage</span><b>></b>English<b>&lt;</b>/<span class="xmlElemTag">moles:datasetLanguage</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:metadataLanguage</span><b>></b>English<b>&lt;</b>/<span class="xmlElemTag">moles:metadataLanguage</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:responsibleParties</span><b>></b>
589<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:responsibleParty</span><b>></b><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:name</span><b>></b>Calum Byrom<b>&lt;</b>/<span class="xmlElemTag">moles:name</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:uri</span><b>></b><b>&lt;</b>/<span class="xmlElemTag">moles:uri</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:role</span><b>></b>Data migrator<b>&lt;</b>/<span class="xmlElemTag">moles:role</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">moles:responsibleParty</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:responsibleParty</span><b>></b><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:name</span><b>></b>Calum Byrom<b>&lt;</b>/<span class="xmlElemTag">moles:name</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:uri</span><b>></b><b>&lt;</b>/<span class="xmlElemTag">moles:uri</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:role</span><b>></b>Data curator<b>&lt;</b>/<span class="xmlElemTag">moles:role</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">moles:responsibleParty</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">moles:responsibleParties</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:abbreviation</span><b>></b>ANON<b>&lt;</b>/<span class="xmlElemTag">moles:abbreviation</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:providerID</span><b>></b><b>&lt;</b>/<span class="xmlElemTag">moles:providerID</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:created</span><b>></b>2008-12-23T13:45:59Z<b>&lt;</b>/<span class="xmlElemTag">moles:created</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">moles:molesISO</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">moles:entity</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">moles:temporalRange</span><b>></b>1901-01-01/2003-04-29<b>&lt;</b>/<span class="xmlElemTag">moles:temporalRange</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">georss:where</span><b>></b>
590<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">gml:Envelope</span><b>></b>
591<div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">gml:lowerCorner</span><b>></b>-29 -02<b>&lt;</b>/<span class="xmlElemTag">gml:lowerCorner</span><b>></b></div><div class="xmlElem"><b>&lt;</b><span class="xmlElemTag">gml:upperCorner</span><b>></b>44 89<b>&lt;</b>/<span class="xmlElemTag">gml:upperCorner</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">gml:Envelope</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">georss:where</span><b>></b></div><b>&lt;</b>/<span class="xmlElemTag">entry</span><b>></b></div></div>
593                    </p>
594                    </div>
595                    <a name="example"><h2>Appendix B: Creating an example set of metadata documents</h2></a>
596                                <div class="headingblock">                 
597                    <p>
598                    Setting up a collection of metadata documents is described in the following example:
599                    <dl>
600                    <dt>
601                    <b>
602                    1. Create a Data Granule atom
603                    </b>
604                    </dt>
605                    <dd>
606                    <ol>
607                    <li>
608                    From the <a href="${h.url_for('home')}">atom home page</a>, click on <a href="${h.url_for('create')}">Create atom</a> link.
609                    </li>
610                    <li>
611                    Select the required Provider ID and select, 'Data Granule' as the Data Type.
612                    </li>
613                    <li>
614                    Click 'Create'.  The editor will now complain about missing author and title data - so provide these.
615                    </li>
616                    <li>
617                                The editor will create a new Data Granule atom and open this in the main editor page.  Add additional
618                                information by editing the different sections and clicking 'Update' each time.
619                    </li>
620                    </ol>
621                    </dd>
622                    <dt>
623                    <b>
624                    2. Create a Data Entity atom and link the Data Granule atom
625                    </b>
626                    </dt>
627                    <dd>
628                    <ol>
629                    <li>
630                    Return to the home page, clicking on the <a href="${h.url_for('home')}">Home</a> link.
631                    </li>
632                    <li>
633                    Click on <a href="${h.url_for('create')}">Create atom</a> link and create a new atom - this type specifying 'Data Entity' as the data type.
634                    </li>
635                    <li>
636                    Add additional data to the Data Entity document; notice there are several extra inputs available
637                    </li>
638                    <li>
639                    Click the 'Add' link in the 'Associated Data Granules' section - this will open the <a href="${h.url_for('list')}">atom search</a> page.
640                    </li>
641                    <li>
642                    Leave the filter blank in its initial state and click, 'Search'.  The Data Granule created in
643                    the previous section should now be displayed.  Gain familiarisation with the search filter,
644                    try changing the selected provider ID and entering search terms - with and without wildcards
645                    (see section '<a href="#searching">Searching atoms</a>' for details).
646                    </li>
647                    <li>
648                    Select the Data Granule created in the previous section, by clicking its checkbox
649                    and then click 'Add Selections'.  The editor will now return to the Data Entity atom; notice
650                    it now displays the Data Granule just added in its 'Associated Data Granules' section.
651                    </li>
652                    <li>
653                    Click on the link to Data Granule in the 'Associated Data Granules' section.  When this
654                    loads notice the 'Associated Data Entities' section now contains the Data Entity to which this atom
655                    has just been associated.
656                    </li>
657                    </ol>
658                    </dd>
659                    <dt>
660                    <b>
661                    3. Create Activity, Observation Station and DPT atoms
662                    </b>
663                    </dt>
664                    <dd>
665                    <ol>
666                    <li>
667                    Return to the home page, clicking on the <a href="${h.url_for('home')}">Home</a> link.
668                    </li>
669                    <li>
670                    Click on <a href="${h.url_for('create')}">Create atom</a> link and create a new atom - this type specifying 'Activity' as the data type.
671                    </li>
672                    <li>
673                    Add additional data to the Activity atom; notice, again, the slightly different available content for input.
674                    </li>
675                    <li>
676                    Repeat steps 2. and 3., specifying Data Types of 'Observation Station' and 'Data Production Tool'
677                    </li>
678                    </ol>
679                    </dd>
680                    <dt>
681                    <b>
682                    4. Create a Deployment atom and link to Deployment Data atoms
683                    </b>
684                    </dt>
685                    <dd>
686                    <ol>
687                    <li>
688                    Return to the home page, clicking on the <a href="${h.url_for('home')}">Home</a> link.
689                    </li>
690                    Click on <a href="${h.url_for('create')}">Create atom</a> link and create a new atom - this type specifying 'Deployment' as the data type.
691                    <li>
692                    Click the 'Add' link in the 'Associated Data' section then search for and add the Deployment Data atoms created in the previous section.
693                    </li>
694                    <li>
695                    The editor will now return to the Deployment atom; notice
696                    it now displays the newly added Deployment Data just added in its 'Associated Data' section.
697                    </li>
698                    <li>
699                    Click on a link to one of the Deployment Data atoms.  This will open the data in 'view' mode.
700                    Click the 'Edit' button at the top of the document to open it in edit mode.  Notice that the
701                    'Associated Deployments Data' now displays the other Deployment Data atoms associated with this
702                    one by the newly created Deployment atom.
703                    </li>
704                    </ol>
705                    </dd>
706                    <dt>
707                    <b>
708                    6. Link Deployment atom to Data Entity atom
709                    </b>
710                    </dt>
711                    <dd>
712                    <li>
713                    Return to the home page, clicking on the <a href="${h.url_for('home')}">Home</a> link.
714                    </li>
715                    <li>
716                    Click on <a href="${h.url_for('list')}">Edit/List atoms</a> and search for the Data Entity created previously.
717                    </li>
718                    <li>
719                    Once found, click 'Edit' to view the Data Entity in the editor.
720                    </li>
721                    <li>
722                    Click the 'Add' link in the 'Associated Deployements' section - and use the search filter to find and add the
723                    Deployment atom just created.
724                    </li>
725                    <li>
726                    The editor returns to the Data Entity atom; notice that the 'Associated Deployments'
727                    section now contains the Deployment atom just added.  Also note the 'Associated Deployments Data'
728                    section now contains summary data from the newly added Deployment atom.
729                    </li>
730                    <li>
731                    Click on the plus/minus sign on the 'Associated Deployments Data' section to
732                    view the data at different levels of detail
733                    </li>
734                    <li>
735                    Click on a link to one of the associated Deployment Data atoms.  When this loads notice
736                    the 'Associated Data Entities' section now contains the Data Entity to which this atom
737                    has just been associated (indirectly via the Deployment atom).
738                    </li>
739                    </dd>
740                    </dl>
741                    </p>
742                    </div>
743                    <a name="exampleCurating"><h2>Appendix C: Curating an example set of metadata documents</h2></a>
744                                <div class="headingblock">                 
745                    <p>
746                    Updating a collection of metadata documents is described in the following example (which assumes the previous Appendix has been completed):
747                    <dl>
748                    <dt>
749                    <b>
750                    1. Curate the Deployment details
751                    </b>
752                    </dt>
753                    <dd>
754                    <li>
755                    From the <a href="${h.url_for('home')}">atom home page</a>, click on the <a href="${h.url_for('list')}">Edit/List atoms</a> link and search for and open the Deployment atom created previously.
756                    </li>
757                    <li>
758                    Click on the 'Edit' link for the 'Associated Data' section.
759                    </li>
760                    <li>
761                    Select a couple of the Deployment Data atoms and click 'Remove'.
762                    </li>
763                    <li>
764                    The Deployment atom now updates - when it reloads notice the selected
765                    Deployment Data atoms are no longer referenced.
766                    </li>
767                    <li>
768                    Click on a remaining Deployment Data atom link - and notice, when this loads, that
769                    it has a reduced set of 'Associated Deployments Data'
770                    </li>
771                    </dd>
772                    <dt>
773                    <b>
774                    2. Remove the Deployment atom association to the Data Entity atom
775                    </b>
776                    </dt>
777                    <dd>
778                    <li>
779                    From the <a href="${h.url_for('home')}">atom home page</a>, click on the <a href="${h.url_for('list')}">Edit/List atoms</a> link and search for and open the Data Entity atom created previously.
780                    </li>
781                    <li>
782                    Click the 'Edit' link of the 'Associated Deployments' section, then select the Deployment atom and click 'Remove'.
783                    </li>
784                    <li>
785                    The editor updates the Data Entity - notice that it no longer has any 'Associated Deployments'.
786                    </li>
787                    <li>
788                    Return to the search page and find one of the Deployment Data atoms created previously.
789                    </li>
790                    <li>
791                    When this loads, notice it no longer has any 'Associated Data Entities' information.
792                    </li>
793                    </dd>
794                    <dt>
795                    <b>
796                    3. Remove the Data Granule atom association to the Data Entity atom
797                    </b>
798                    </dt>
799                    <dd>
800                    <li>
801                    Repeat the previous section, but this time remove the atom in the 'Associated Data Granules' section.
802                    </li>
803                    <li>
804                    Check the Data Granule is no longer featured in the Data Entity - and that it no longer references
805                    the Data Entity.
806                    </li>
807                    <li>
808                    Add the Data Granule to the Data Entity again.
809                    </li>
810                    <li>
811                    Now, search for the Data Granule and open in the editor.
812                    </li>
813                    <li>
814                    Click the 'Delete' button at the top of the document and confirm the deletion.  A pop up
815                    box should confirm that the deletion has completed successfully.  Control returns to the
816                    atom home page.
817                    </li>
818                    <li>
819                    Click on <a href="${h.url_for('list')}">Edit/List atoms</a> and search for the deleted Data Granule - it should no longer be found.
820                    Instead return to the Data Entity created previously.
821                    </li>
822                    <li>
823                    Observe the Data Entity no longer holds any data in its 'Associated Data Granules' section;
824                    the Data Granule has been deleted and references to it have been removed.
825                    </li>
826                    </dd>
827                    </dl>
828                    </p>
829                    </div>
830                </div>
831        </div>
832  </body>
Note: See TracBrowser for help on using the repository browser.