You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful if all projects could be identified in a contiguous fashion.
Perhaps the title prefixed.
MyORG-ZZZZ - Textual title which can be changed
Where MyORG-ZZZZ is generated by Coldfront, thus all projects titles are created in sequence, and the submitter of the project request can only have the freedom to specify the Textual title, 2nd half of the overall Project title.
Update: on reflection, this may be better as an internal project ID field. That is not editable, and is separate from the title field. This field would be viewable by PI/manager/user etc. It would not be editable by anyone. It would increment appropriately.
The internal project ID field, would allow centre staff and users to refer to a common project ID.
MyORG-ZZZZ
As seen in django this would be
PK
Internal project ID
1
MyOrg1001
2
MyOrg1002
3
MyOrg1003
...
...
Beyond the immediate use of an internal project ID field, is later the ability to create LDAP groups based on this field, via a plugin. This is outside of the scope of this initial Issue. Here it is only proposed that an incrementing internal project ID field is created.
Component
Projects
Additional information
No response
The text was updated successfully, but these errors were encountered:
Description
It would be useful if all projects could be identified in a contiguous fashion.
Perhaps the title prefixed.MyORG-ZZZZ - Textual title which can be changed
Where MyORG-ZZZZ is generated by Coldfront, thus all projects titles are created in sequence, and the submitter of the project request can only have the freedom to specify the Textual title, 2nd half of the overall Project title.Update: on reflection, this may be better as an internal project ID field. That is not editable, and is separate from the title field. This field would be viewable by PI/manager/user etc. It would not be editable by anyone. It would increment appropriately.
The internal project ID field, would allow centre staff and users to refer to a common project ID.
MyORG-ZZZZ
As seen in django this would be
Beyond the immediate use of an internal project ID field, is later the ability to create LDAP groups based on this field, via a plugin. This is outside of the scope of this initial Issue. Here it is only proposed that an incrementing internal project ID field is created.
Component
Projects
Additional information
No response
The text was updated successfully, but these errors were encountered: