Additional notification options

[computerprep 142]

1) {UserName} has logged in

2) Metadata { for {ItemName} has been manually changed by {UserName}

3) {UserName} has initialized downloading {ItemName)

 

I think these descriptions above speak for themselves. Please ask if you need clarification on what I mean by any of them.

 

Idea #2 would pair very nicely with a recursion capability in textual metadata storage. Without recursion, this notification would also need to inform us which specific metadata field was edited, but it would not recall what it was before the change.

 

True recursion may not be feasible for all metadata considering potential image filesizes, but for images that were fetched through linked sources, the link or path to that source file could be recursively archived.

 

Let me know if you think I should add separate feature request for metadata recursion. It's true, I have had a few problems with users changing metadata improperly. In my scenario, I can't just remove them from administrative capability.

Edited December 17, 2015 by computerprep

[Luke 37116]

yes good ideas.