Closed spalp closed 8 months ago
Thank you for reporting the issue. I'll have a look
That's actually an expecting behaviour. IPT manual https://ipt.gbif.org/manual/en/ipt/latest/manage-resources#publication
Once the resource is registered only users with the role "Manager with registration rights" can publish, since the resource’s registration gets updated during each publication
Thanks, Mikhail. I suspected this but wasn't sure. Apologies for not checking thoroughly in advance before posting here.
============
Salza Palpurina
GBIF Europe and Central Asia Regional Support Team
@.*** | skype hecksa
https://www.gbif.orghttps://www.gbif.orgo
From: Mikhail Podolskiy @.> Sent: Saturday, February 10, 2024 9:13:58 PM To: gbif/ipt @.> Cc: Salza Palpurina @.>; Author @.> Subject: Re: [gbif/ipt] Manager (withour registration rights) not allowed to publish new versions after registering the resource (Issue #2319)
That's actually an expecting behaviour. IPT manual https://ipt.gbif.org/manual/en/ipt/latest/manage-resources#publication
Once the resource is registered only users with the role "Manager with registration rights" can publish, since the resource’s registration gets updated during each publication
— Reply to this email directly, view it on GitHubhttps://github.com/gbif/ipt/issues/2319#issuecomment-1937099314, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC2SQ5PDHHHICKQVA5IJP4LYS7BHNAVCNFSM6AAAAABCTF52ESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGA4TSMZRGQ. You are receiving this because you authored the thread.Message ID: @.***>
I'll have a look why new version may publish on update. I'm closing this one.
Hi there,
As regards the following dataset: https://cloud.gbif.org/eca/manage/resource?r=atlas_breeding_birds_bulgaria_2007, the author (a manager without registration rights) stopped being able to publish new versions after the source has been registered.
Even stranger, two days ago, when the dataset was not yet registered, each time he refreshed the resource page, a new version was published even though the auto-publication setting was off. This behaviour has now stopped but, as described above, now he cannot publish anymore (but I - as admin - can).
We tested with another resource that he created for a testing purpose: he could publish new versions of that new source (at least before registration) but still not of the other one. I am not sharing the link because we did not register the test resource but deleted it instead.
Any idea why this strange behaviour?
@ManonGros removed the same manager and then re-assigned him again. He logged out and deleted the browser's cash but the same error still appeared.