Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strategic Partnerships #15

Open
monicamcjunkin opened this issue May 16, 2019 · 2 comments
Open

Strategic Partnerships #15

monicamcjunkin opened this issue May 16, 2019 · 2 comments

Comments

@monicamcjunkin
Copy link
Contributor

Support for strategic partnerships is one of our highest priority capabilities for the Operating System.

Initial thoughts on how this might work is is detailed here:
https://docs.google.com/document/d/1D7kyXzrOXdkMINRA2a--adRK96STr1AhNFU8Do2jACw/edit

Kicking off further discussion:
One potential area for exploration - How do we do tagging? What is meant by 'democratic tagging'? If these are assigned manually, is there any taxonomy or vocabulary control to ensure that similar topics are linked?

@PhilNorman2
Copy link
Contributor

So tagging allows a user (usually a signed in user) to add a term to the keyword index associated with a particular item. For example, when a user is viewing an SCOS record for a food pantry dataset she could tag the record with the term "food bank". When other users searched the SCOS database with the keyword "food bank" the results would include the food pantry dataset and the tag would appear as a keyword in the left panel.

At its simplest there would be a button that the user would click to get to a form where he would enter tag(s) and submit.

I am guessing democratic tagging means as few constraints as possible. Should the user be required to log in? That could be a barrier to keep bad actors from adding inappropriate tags. From my experience adding tags requires some amount of oversight. Where I used to work we had individuals in-house approve tags before they were were activated in the keyword index.

I think we were leaning away from a formal taxonomy for the user tags. However, there is a taxonomy for nonprofits which could be useful for metadata for the organization. Should the source for that metadata be limited to the supplying org or curator using that taxonomy?

I am not so sure we have to answer all those questions in the report, maybe rather we include the questions for SCOS to answer.

@PhilNorman2
Copy link
Contributor

I am thinking "Support for Strategic Partnerships" is more a value stream/theme than a feature. Would it be useful to add epics/user stories based on what we touched on as well as less complex features that add value? For example something like the following:

  1. As a non-profit business owner I need to identify organizations that have synergistic business values so I can create strategic partnerships to add more value to the clients of our respective organizations.

1.1 As a data provider I want to see the corresponding organizations in the results so I can provide attribution (form of advertising).

1.2 As a nonprofit business analyst I want these organizations in the results to be hot linked to the organization home page so I learn more about the organization to support relationships, e.g., goals and contact information.

1.3 As a nonprofit business owner I want to see the totality of the organizations in one place and the types of datasets they provide in order to facilitate the creation of strategic business partnerships. (A tag cloud is a solution to this problem)

  1. As a non-profit analyst I need to be able to locate SCOS datasets that have synergistic relationships with my data so I can use that data to solve problems for my clients and support my business case to stakeholders.

2.1. As a nonprofit business analyst I want to see the totality of types of datasets in one place in order to target the data I can use to solve problems for my clients. (again tech cloud is the solution)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants