Uploaded image for project: 'VIVO'
  1. VIVO
  2. VIVO-281

Consider whether extended linked data can/should be made optional in configuring a VIVO installation

    Details

    • Attachments:
      0
    • Comments:
      6

      Description

      Mike Conlon commented at the conference that VIVO's linked data returns much more data than he thinks is necessary for a linked data request, affecting performance. This has been done consciously (see https://issues.library.cornell.edu/browse/NIHVIVO-3152, https://issues.library.cornell.edu/browse/NIHVIVO-3601), based on early feedback suggesting that limiting the number of requests needed to obtain a useful response, but it would be helpful to be able to state what we do, whether the "extended" aspect is configurable, and whether we think it should or should not be configurable.
      Unless trivial to implement any changes would have to be planned for a future release.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                j2blake Jim Blake
                Reporter:
                jc55 Jon Corson-Rikert
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified