Init1dbw13 - Forms Services

Date: 

03/10/2010

Requirement # unique id <SemConOps Initiative>.<analysts initials><requirement number>
e.g. Init1dbw1
(eventually linked to Use Cases)

Init1dbw13

Originator/Customer's Name:

Bob Friemuth for AGNIS Metadata Tool

Originator/Customer's Company:

Mayo

Summary of requirement initial analysis, by Reviewer: (as unambiguously as possible, describe who (List of Actors) is interacting with the system, what the business goal is and how the system might support the actor's ability to acheive their goal)

In the course of retrieving the metadata for a CRF from the caDSR, the
metadata curator using the generates a request to retireve a Form from caDSR. The AGNIS Metadata Tool sends a large number of web service requests to the cadsrapi40Service web service. This can take a long time, due to the large number of round trips to the server. One possible way to improve performance would be to implement a caDSR API that, instead of returning only one object at a time, could return a graph of objects in response to a single web service request. This would move processing to the server side, where it can be done more efficiently, and also improve performance by reducing the number of round trips to the server.
For example, a caDSR client tool such as the AGNIS Metadata Tool might benefit from an API capable of returning a graph of objects such as the following in response to a single query.  
The RULES (skip to/from instructions, default values or repeating group information) around the question might also be useful, such as the order of the question in the form.


> Question
>   |-- definitionCollection
>   |-- designationCollection
>   |-- instruction
>   |-- dataElement
>   |     |-- dataElementConcept
>   |     |    |-- definitionCollection
>   |     |    |-- designationCollection
>   |     |    +-- referenceDocumentCollection
>   |     |          +-- attachments
>   |     |-- definitionCollection
>   |     |-- designationCollection
>   |     |-- referenceDocumentCollection
>   |     |    +-- attachments
>   |     +-- valueDomain
>   |           |-- definitionCollection
>   |           |-- designationCollection
>   |           +-- referenceDocumentCollection
>   |                 +-- attachments
>   |-- referenceDocumentCollection
>   |     +-- attachments
>   +-- validValueCollection
>         |-- definitionCollection
>         |-- designationCollection
>         |-- instruction
>         |-- referenceDocumentCollection
>         |     +-- attachments
>         +-- valueDomainPermissibleValue
>              +-- permissibleValue
>                    +-- valueMeaning
>                           |-- definitionCollection
>                           |-- designationCollection
>>>>>>>>>>>>>>>>>>>>>>>>>>>>|-- conceptCollection
>                           +-- referenceDocumentCollection
>                                 +-- attachments
>  

Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room

Use Case Template to describe the 'graph' in more detail