Search the catalog - Revision history

Jimg: /* Triggers */

2010-01-13T18:39:49Z

Triggers

← Older revision		Revision as of 18:39, 13 January 2010
Line 39:		Line 39:
	== Triggers ==		== Triggers ==
	<font size="-2" color="green">''Here we describe in detail the event or events that brings about the execution of this use case. Triggers can be external, temporal, or internal. They can be single events or when a set of conditions are met, List all triggers and relationships.''</font>		<font size="-2" color="green">''Here we describe in detail the event or events that brings about the execution of this use case. Triggers can be external, temporal, or internal. They can be single events or when a set of conditions are met, List all triggers and relationships.''</font>

			* The user wants to find data.

	== Basic Flow ==		== Basic Flow ==

Jimg: /* Preconditions */

2010-01-13T18:39:02Z

Preconditions

← Older revision		Revision as of 18:39, 13 January 2010
Line 34:		Line 34:
	== Preconditions ==		== Preconditions ==
	<font size="-2" color="green">''Here we state any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case. Any assumptions about other systems can also be stated here, for example, weather conditions. List all preconditions.''</font>		<font size="-2" color="green">''Here we state any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case. Any assumptions about other systems can also be stated here, for example, weather conditions. List all preconditions.''</font>

			* The NcML for a group of datasets has been written and those datasets have been crawled and cataloged by some Metacat server.

	== Triggers ==		== Triggers ==

Jimg: /* Actors */

2010-01-13T18:37:36Z

Actors

← Older revision		Revision as of 18:37, 13 January 2010
Line 25:		Line 25:
	== Actors ==		== Actors ==
	<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>		<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>

			* The user searching for data
			* Kepler and its search interface, modified to work with metadata records that contain SpatialRaster elements
			* Metacat
			* DAP servers
			* NcML files

	== Preconditions ==		== Preconditions ==

Jimg: /* Goal */

2010-01-13T18:33:04Z

Goal

← Older revision		Revision as of 18:33, 13 January 2010
Line 11:		Line 11:
	<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>		<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>

	A user wants to find data so they search a given catalog and are shown a set of URLs which reference data sets ~~(ones relevant to~~ the search~~...)~~.		A user wants to find data so they search a given catalog and are shown a set of URLs which reference data sets that have metadata records matching the search parameters.

	== Summary ==		== Summary ==

Jimg: /* Summary */

2009-03-02T23:46:41Z

Summary

← Older revision		Revision as of 23:46, 2 March 2009
Line 17:		Line 17:

	A user is working with the Kepler system (a client from the perspective of a DAP server) and wants to search for data (i.e., for data sets that contain data from a certain time or range of times, location or within a bounding box and/or that are described by one or more keywords). Since Kepler already is designed to search over EML records stored in one or more Metacat servers, that search system will be used by this system.		A user is working with the Kepler system (a client from the perspective of a DAP server) and wants to search for data (i.e., for data sets that contain data from a certain time or range of times, location or within a bounding box and/or that are described by one or more keywords). Since Kepler already is designed to search over EML records stored in one or more Metacat servers, that search system will be used by this system.

			<font color="red">Need to add information about:
			* How Kepler should provide an interface for this; and
			* How we're going to look for satellite data given that Kepler does not currently search over geo-spatial EML records
			</font>

	== Actors ==		== Actors ==

Jimg at 20:06, 2 March 2009

2009-03-02T20:06:31Z

← Older revision		Revision as of 20:06, 2 March 2009
Line 1:		Line 1:
	'''Point Of Contact:''' ~~''A Human''~~		'''Point Of Contact:''' James

			[[REAP Cataloging and Searching]]

	== Description ==		== Description ==

Jimg: /* Summary */

2009-03-02T20:05:40Z

Summary

← Older revision		Revision as of 20:05, 2 March 2009
Line 14:		Line 14:
	<font size="-2" color="green">''Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.''</font>		<font size="-2" color="green">''Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.''</font>

	A user is working with the Kepler system (a client from the perspective of a DAP server) and wants to search for data (i.e., for data sets that contain data ~~which can be~~ described ~~as containing information about ''X''~~). Since Kepler already is designed to search over EML records stored in one or more Metacat servers, that search system will be used by this system.		A user is working with the Kepler system (a client from the perspective of a DAP server) and wants to search for data (i.e., for data sets that contain data from a certain time or range of times, location or within a bounding box and/or that are described by one or more keywords). Since Kepler already is designed to search over EML records stored in one or more Metacat servers, that search system will be used by this system.

	== Actors ==		== Actors ==

Jimg: /* Summary */

2009-02-27T01:43:15Z

Summary

← Older revision		Revision as of 01:43, 27 February 2009
Line 13:		Line 13:
	== Summary ==		== Summary ==
	<font size="-2" color="green">''Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.''</font>		<font size="-2" color="green">''Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.''</font>

			A user is working with the Kepler system (a client from the perspective of a DAP server) and wants to search for data (i.e., for data sets that contain data which can be described as containing information about ''X''). Since Kepler already is designed to search over EML records stored in one or more Metacat servers, that search system will be used by this system.

	== Actors ==		== Actors ==
	<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>		<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>

Jimg: /* Goal */

2009-02-27T01:39:40Z

Goal

← Older revision		Revision as of 01:39, 27 February 2009
Line 8:		Line 8:
	== Goal ==		== Goal ==
	<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>		<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>

			A user wants to find data so they search a given catalog and are shown a set of URLs which reference data sets (ones relevant to the search...).

	== Summary ==		== Summary ==

Jimg: /* Description */

2009-02-27T01:38:06Z

Description

← Older revision		Revision as of 01:38, 27 February 2009
Line 3:		Line 3:
	== Description ==		== Description ==
	<font size="-2" color="green">''Give a short descriptive name for the use case to serve as a unique identifier.''</font>		<font size="-2" color="green">''Give a short descriptive name for the use case to serve as a unique identifier.''</font>

			Search00

	== Goal ==		== Goal ==