search

DSpace / dspace-angular

DSpace User Interface built on Angular.io
https://wiki.lyrasis.org/display/DSDOC8x/
BSD 3-Clause "New" or "Revised" License
125 stars 416 forks source link

Make EPerson "Contact Telephone" field available for Administrators via GUI #2692

Open Taurus2024 opened 9 months ago

Taurus2024 commented 9 months ago

Is your feature request related to a problem? Please describe. Administrator can see and edit data in EPerson "Contact Telephone" field via GUI of Dspace v6.x. Administrator can not see and edit data in EPerson "Contact Telephone" field via GUI of Dspace v7.x.

Describe the solution you'd like It would be great to allow Administrator to see and edit EPerson "Contact Telephone" field via GUI of Dspace v7.x in the same way as in Dspace v6.x.

Additional context image image

tdonohue commented 9 months ago

Agreed, this seems reasonable. Moving this ticket to the 8.0 board in search of a volunteer. It might not be a difficult task (assuming that the REST API already supports modifying the Phone field).

Taurus2024 commented 9 months ago

Hi @tdonohue , thank you. I have one question: is it possible to move this ticket to 7.x board instead of 8.0? Because there was information: New features added to 7.6 will concentrate entirely on feature parity with 6.x in order to achieve feature completeness. Therefore, new features will only be accepted into 7.6 if they previously existed in 6.x (or below). All other new features will be rescheduled for 8.0 And this feature exists in 6.x and missed in 7.x.

tdonohue commented 9 months ago

@Taurus2024 : That was information specific to 7.6 (which was released on June 23 of this year). If you read that full announcement it notes this:

Therefore, the DSpace Steering Group would like to announce that the 7.x platform will move into “maintenance mode” immediately after the 7.6 release.

  • No new features will be added to the 7.x platform after 7.6. Instead, all future releases of 7.x will be bug-fix only releases.

Because 7.6 has been released, this means no more new features will be added to 7.6.x regardless of whether the feature was in 6.x.

All that said, if the person who volunteers to tackle this ticket finds that this fix is very minor, at that point we could recategorize it as a "bug fix" and allow it in a 7.6.x release. But, if they find this is a "new feature" and requires significant improvements to both the backend and frontend, then this will need to stay scheduled for 8.0.

Hopefully that explains things better. Overall, this is waiting on a volunteer to tackle it, regardless of which release it ends up in.

Taurus2024 commented 9 months ago

Hi @tdonohue, thank you for the detailed feedback. It is clear now.

PitbaranK commented 1 month ago

Hi Tim, We'd like to claim #2692.

tdonohue commented 1 month ago

@PitbaranK : Assigning to you. (When you get a chance, could you add your organization, Virsoftech, in your GitHub profile in some manner? It's really helpful to me when I'm writing future release notes, as it's a reminder to me that these tickets should be credited back to Virsoftech.)