This use case represents a flow where faculty interact directly with VIVO, or an interface above VIVO, updating their profile and a Fedora repository front-end, uploading publications. The uploaded publications would transparently be stored in an integrated, backend Fedora 4would trigger a messaging event from Fedora 4 that would be consumed by a message listener (such as the fcrepo-camel-toolbox), and result in an update to VIVO via its HTTP API.