Skip to content
← Customer Feedback for UW Web Services

Settings and activity

2 results found

  1. allow potential service consumers to limit their usage authorization request to only the less sensitive resources

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  University of Washington API and Web Services » fws  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    acknowledged  ·  Tony Chang responded

    We definitely recognize this is a real problem. We plan on working with the FWS data stewards to see if we can develop a lighter weight process for certain resources.

    Shawn Medero supported this idea  · 

  2. Provice access to campus research information - who is doing what where...

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    acknowledged  ·  4 comments  ·  University of Washington API and Web Services » research  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Shawn Medero supported this idea  · 
    An error occurred while saving the comment
    Shawn Medero commented  · 

    I am wondering how the original poster envisioned this idea would work. What level of specificity would be useful? Are you just trying to obtain a list of researchers working in a fairly high level "large problem space"? Are you trying to get specific details about researchers tied to funding source? Do you want a text mining service that is crawling and indexing all of the papers being written by researchers at UW? There are a lot of ways to tackle the question described and I wouldn't begin to know how to crack this nut without some more detailed use cases.