Main content



Loading wiki pages...

Wiki Version:
<h3>Use cases overview</h3> The [RMap grant proposal][1] described seven use cases, or, perhaps more accurately, user scenarios, to illustrate how and why people and systems in different roles and capacities might interact with and make use of the RMap service. Starting from these scenarios, the RMap team conducted a series of use cases “brainstorming” sessions, developing a list of candidate use cases into to which they drilled down, elaborating in detail some of those use cases. The technical team employed the detailed use cases to develop the RMap data model and RMap low-level RESTful API. The following use case documents were produced: 1. [Use Case overview][2] 2. [Use Case brainstorming][3] 3. [Academic institution request for articles referencing datasets created by researchers affiliated with the institution][4] 4. [Author submission to publisher][5] 5. [Data repository's referencing article list synchronization][6] 6. [Funder use case 01: Query via funder grant identifier][7] 7. [Funder use case 02: Query via FundRef name or identifier][8] 8. [Preservation status use case: Grant funder or author wishes to determine preservation status of research artifact][9] 9. [Publisher query to RMap][10] 10. [Researcher/author submission - Author mediated][11] 11. [Researcher/author submission - RMap mediated][12] 12. [Software use case 1: Developer(s) of a scientific software wish to link source code, binaries, and other resources][13] 13. [Software use case 2: Adding links to software releases to RMap][14] 14. [Software use case 3: Application of software used in research to original data and to variations of data][15] 15. [Software use case 4: .EXE preservation archive curating software][16] These documents were last updated on February 26, 2015. [1]: [2]: [3]: [4]: [5]: [6]: [7]: [8]: [9]: [10]: [11]: [12]: [13]: [14]: [15]: [16]: