I believe items have disappeared from our company layer created in the portal. Not all of them, but I’m noticing several that I know were created close to a year ago that are no longer there.
Is there something that could’ve happened to cause this?
I believe items have disappeared from our company layer created in the portal. Not all of them, but I’m noticing several that I know were created close to a year ago that are no longer there.
Is there something that could’ve happened to cause this?
I’ve never known that to happen and can’t think of any reason it would, other than someone actually explicitly deleting them. I can do a little poking around in the database to see if I can find anything if you like, though. Can you tell me anything specific about the items, ideally exact names?
I do not have a backup of the exact names, and more than one person has the ability to add and delete items, so it was likely accidental throughout time. I just was curious if there was anything on the backend migration etc. that could’ve caused this.
If they were deleted recently, they can be recovered using “Layers > Deleted”, but items only hang out there for about a week.
Is there a way to lock a layer so only a specific group can modify it?
I already have myself and another in a group called Chart Administrators and only we can turn it off our chart display. Limiting the ability to edit this particular layer to that group would be useful.
I’m not sure what you mean by “group” here…the portal has vessel groups, but does not have a way to group members.
The other Port Captain and I have full licenses attached to our accounts. Is what I referring to, I have grouped him and myself as a vessel type to be able to disable the company’s portal layer from viewing when we open Rose Point ECS to do investigations (this is an old carry over from when the Portal didn’t have playback feature)
I’m asking for the ability to lock a layer from being modified in the portal to just a select group of members, as it stands right now anybody with portal access (dispatcher, maintenance tech, etc..) could theoretically delete a mark, and as you stated if it happened longer than a week ago and I didn’t notice it’s just gone.
I see… We have another request for the ability to lock layers, but it has more to do with preventing accidental changes than completely preventing someone from making changes (in that it would just be a lock/unlock option that anyone could change). Would something like that solve your problem or do you really want some way to make sure only certain people could make changes?
It has also been brought to my attention that portal viewers can make changes to items in fleet layers. That is not supposed to be allowed and will be fixed soon. Would that solve your problem?
Locking portal viewers or locking a layer would work in my case. As long as I had a way to differentiate or designate people that DO have the ability.
@brad I’m definitely losing marks on our company layer. Specifically I’m missing a few on the IL River and Ohio river now that our vessels are reporting back. I exported the layer to a .NOB as a reference to use, is there a way to extend out how long deleted items are retained in the list?
I had custom marks on every lock on the Arkansas, Ohio, and Illinois River.
There is not currently a way to extend that time. However, I can still perform some forensics on your database if you’d like. If I can find a delete item I can tell you when it was deleted and I might even be able to tell who was using the portal around that date and time.
Any chance you can give me the exact title of a missing mark from your export?
“Cannelton Lock Procedure”
Would’ve been an “Information” blue mark with a filled boundary circle around it probably 300’ diameter near OHR MM721
Thanks, but unfortunately I was not able to find any trace of that so it must have been purged a while ago. We’ve added some logging that will record deletions along with the user that performed the delete. This is part of a more general logging feature that will be added to the portal in the future that is not ready to be enabled for all users yet, so only I can look at the logs at this point. So if this happens again, let me know and I can check the logs for you. We are also considering other ways of dealing with, or ideally preventing, problems like this.
Thank you for your efforts and consideration with this problem!