Purpose: Given the vast range of domain knowledge involved in software and system history in identified EAASI use cases, collaboration between multiple individuals is frequently necessary for proper configuration and troubleshooting of Environments. At the same time, given collection restrictions and other concerns, this sharing and collaboration must be knowingly limited to specific user accounts. Resource creator accounts in EAASI (Organization Administrators and Configuration Users) need to allow another individual resource creator account to access their (initially) private resources.
Ideally, the initial Organization Administrator or Configuration User account should be able to set the second account’s read/write permissions with the shared resource at the point of sharing.
Gap Analysis: All EAASI resources are Private (available both read/write) the user account that initially imported or created them. The only method to make resources accessible at all to any other user account, regardless of Organization, is to Publish them via OAI-PMH, which makes the resource immediately accessible (read-only) to all user accounts in the deployment across all Organizations, as well as to other EAASI deployments, if they have the origin deployment’s OAI-PMH info (provider endpoint URL and API key).
Currently, a link to a resource can be copied from the URL bar and shared with other users who already have access to that resource. When the user clicks the link, they are prompted to log in and then they are taken to the page for the resource. The link is generic and is not customized or tailor-made for a specific user.
Purpose: Given the vast range of domain knowledge involved in software and system history in identified EAASI use cases, collaboration between multiple individuals is frequently necessary for proper configuration and troubleshooting of Environments. At the same time, given collection restrictions and other concerns, this sharing and collaboration must be knowingly limited to specific user accounts. Resource creator accounts in EAASI (Organization Administrators and Configuration Users) need to allow another individual resource creator account to access their (initially) private resources.
Ideally, the initial Organization Administrator or Configuration User account should be able to set the second account’s read/write permissions with the shared resource at the point of sharing.
Gap Analysis: All EAASI resources are Private (available both read/write) the user account that initially imported or created them. The only method to make resources accessible at all to any other user account, regardless of Organization, is to Publish them via OAI-PMH, which makes the resource immediately accessible (read-only) to all user accounts in the deployment across all Organizations, as well as to other EAASI deployments, if they have the origin deployment’s OAI-PMH info (provider endpoint URL and API key).
Currently, a link to a resource can be copied from the URL bar and shared with other users who already have access to that resource. When the user clicks the link, they are prompted to log in and then they are taken to the page for the resource. The link is generic and is not customized or tailor-made for a specific user.