Provenance object property - an internally facing property in which editors log purposeful deviations between VIVO and the system of record

Description

Has anyone ever thought about requesting a provenance object property - that is, an internally facing property in which editors such as me can keep track of who told whom (and when) that the URL or a name for an org. unit is different than the system of record might suggest. Or, it could be a place to record the rationale for deviating from the system of record. For example, the "official" name for the division that is called Neurobiology is "Division of Neurobiology." Well, we decided for now at least to just call it Neurobiology.

In listing our org. units, we're probably further along than most, and we have run into at least a couple such cases. It would be nice to note the source for some of the more ambiguous objects within VIVO for future reference.

Now maybe this is a half-baked idea, so I don't know if it would be useful in practice. I just wanted to throw this out there and see if other sites might see the same need. If you would, just keep it in the back of your head for future reference.

Environment

None

Activity

Show:
Stella Mitchell (account no longer used)
March 30, 2011, 5:11 PM

In this week's small team meeting we said we'll treat all the issues as Blockers unless specifically decided otherwise for a particular issue. I'm doing a bulk set of all priorities to Blocker and we can lower particular issues on an individual basis.

Assignee

BrianL

Reporter

Paul Albert

Labels

None

Requested By

None

Time tracking

3h

Components

Fix versions

Affects versions

Priority

Blocker
Configure