Setup the catalog infrastructure - Revision history

Jimg: /* Summary */

2010-01-14T22:46:46Z

Summary

← Older revision		Revision as of 22:46, 14 January 2010
Line 15:		Line 15:

	This use case describes how a new catalog site is set up. The process involves getting, installing and configuring the MetaCat server and DAP server crawler. But those steps only put the infrastructure in place, other required activities will include configuring the crawler to scan and catalog a group of servers, writing a document to describe how to add metadata for a particular client or project and probably writing XSLT to build those documents from the datasets' DDX objects.		This use case describes how a new catalog site is set up. The process involves getting, installing and configuring the MetaCat server and DAP server crawler. But those steps only put the infrastructure in place, other required activities will include configuring the crawler to scan and catalog a group of servers, writing a document to describe how to add metadata for a particular client or project and probably writing XSLT to build those documents from the datasets' DDX objects.

			A key thing about this use case is that it requires software development, at least at the level of XSLT.

	== Actors ==		== Actors ==

Jimg: /* Basic Flow */

2010-01-14T22:45:43Z

Basic Flow

@@ Line 31: / Line 31: @@
 == Basic Flow ==
 <font size="-2" color="green">''Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)''</font>
 == Alternate Flow ==

Jimg: /* Summary */

2010-01-14T22:34:55Z

Summary

← Older revision		Revision as of 22:34, 14 January 2010
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>

			This use case describes how a new catalog site is set up. The process involves getting, installing and configuring the MetaCat server and DAP server crawler. But those steps only put the infrastructure in place, other required activities will include configuring the crawler to scan and catalog a group of servers, writing a document to describe how to add metadata for a particular client or project and probably writing XSLT to build those documents from the datasets' DDX objects.

	== 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: /* Actors */

2010-01-14T21:54:41Z

Actors

← Older revision		Revision as of 21:54, 14 January 2010
Line 17:		Line 17:

	* A person who wants to setup a catalog for a particular client or project		* A person who wants to setup a catalog for a particular client or project
	* ~~one~~ or more data servers, likely maintained independently from each other and the catalog		* One or more data servers, likely maintained independently from each other and the catalog
	* a client or project with a specific set of search requirements		* A client or project with a specific set of search requirements

	== Preconditions ==		== Preconditions ==

Jimg: /* Actors */

2010-01-14T21:53:20Z

Actors

← Older revision		Revision as of 21:53, 14 January 2010
Line 15:		Line 15:
	== 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>

			* A person who wants to setup a catalog for a particular client or project
			* one or more data servers, likely maintained independently from each other and the catalog
			* a client or project with a specific set of search requirements

	== Preconditions ==		== Preconditions ==

Jimg: /* Goal */

2010-01-13T19:01:36Z

Goal

← Older revision		Revision as of 19:01, 13 January 2010
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>

			To build both a system that will work for the REAP project and to make one that we can describe as, at minimum, capable of being used in a general context, the design must support many different metadata stores. The goal of this use case is to describe the set up and initialization of a new Metacat that will catalog some collection of DAP data sets.

	== Summary ==		== Summary ==

Jimg: /* Description */

2010-01-13T18:48:08Z

Description

← Older revision		Revision as of 18:48, 13 January 2010
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>

			SystemConfiguration00

	== Goal ==		== Goal ==

Jimg: New page: {{subst:Template:Use_Case}}

2010-01-13T18:47:35Z

New page: {{subst:Template:Use_Case}}

New page

'''Point Of Contact:''' ''A Human''

== Description ==
''Give a short descriptive name for the use case to serve as a unique identifier.''

== Goal ==
''The goal briefly describes what the user intends to achieve with this use case.''

== Summary ==
''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.''
== Actors ==
''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.''

== Preconditions ==
''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.''

== Triggers ==
''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.''

== Basic Flow ==
''Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)''

== Alternate Flow ==
''Here we give any alternate flows that might occur. May include flows that involve error conditions. Or flows that fall outside of the basic flow.''

== Post Conditions ==
''Here we give any conditions that will be true of the state of the system after the use case has been completed.''

== Activity Diagram ==
''Here a diagram is given to show the flow of events that surrounds the use case.''

== Notes ==
''There is always some piece of information that is required that has no other place to go. This is the place for that information.''

== Resources ==
''In order to support the capabilities described in this Use Case, a set of resources must be available and/or configured. These resources include data and services, and the systems that offer them. This section will call out examples of these resources.''

{| cellspacing="0" border="1"
|Resource
|Owner
|Description
|Availability
|Source System
|-
|''name''
|''Organization that owns/ manages resource''
|''Short description of the resource''
|''How often the resource is available''
|''Name of system which provides resource''
|}