Page Comparison

Announcements and discussion

Old business tickets

Patrick

New comments on ticket and on April Dev Pri meeting notes.

Patrick

Decision notes from May:

Leave comment asking for a suggestion of what it should look like.

Awaiting More Info. If a good answer comes in, then we can pass or close based on that.

Reviewing Ready for Development tickets: Bug kanban board (##/58 tickets)

Terra

1. ANW-149

   1. yes

   2. yes

   3. not sure/phydesc imported fine for me.

2. ANW-170

   1. yes

   2. yes

   3. no (works correctly in sandbox). But, I agree about maybe changing date picker, so it doesn’t block ‘date expression’ field.

3. ANW-365

   1. yes

   2. yes

   3. ask Christine if updated based on other ticket updates.

4. ANW-369

   1. yes

   2. no? higher priority re: accessibility?

   3. yes

Alicia

1. ANW-347

   1. y

2. ANW-234

   1. y

3. ANW-251

4. ANW-262

   1. n

5. ANW-261

   1. n

   2. Same issue as above

Edgar

1. ANW-694

   1. Yes

   2. It still appears that the whole citation generation process has an issue, should the ticket be updated?

2. ANW-705

   1. No

   2. This is stale (a year old) and no update was provided on specifics of where span tags are being problematic. Recommend closing.

3. ANW-724

   1. No?

   2. Priority is set to Major.

4. ANW-736

   1. Yes

   2. The bug might be difficult to find/fix but otherwise should be ok for a Community Developer to attempt it.

5. ANW-739

   1. Yes

6. ANW-750

   1. Yes

7. ANW-751

   1. Yes?

   2. Priority is Major but it seems doable.

8. ANW-752

   1. Yes

9. ANW-757

   1. Yes

   2. Priority is Major but should this be set to Minor?

Maggie

1. ANW-758

   1. No – because involves different problems with SUI pdf exports and PUI pdf exports

   2. n/a

2. ANW-760

   1. No – priority is major

   2. n/a

3. ANW-782

   1. Yes? – minor priority and explains changes in code needed

4. ANW-783

   1. No – major priority and involves search

5. ANW-784

   1. No? – think this is a “nice to have” and tagged as a bug and minor, but the standards aspect + importer/exporter make me think it might be complicated

   2. Overlaps with Patrick’s answer re: ANW-504

6. ANW-787

   1. Yes?

   2. Not sure exactly what this is describing, tabbing through seemed fine, can Laney offer clarification in description?

7. ANW-792

   1. Yes? – minor bug, however changes needed aren’t described

8. ANW-823 – this issue is now CLOSED

9. ANW-880

   1. No – might have been a good candidate (especially with Dartmoth plugin) however it looks like work is already being no on it

William

Lydia

1. ANW-249

   1. maybe? it sounds as simple as adding “Identifier” to the sort dropdown menu and its resulting action

   2. minor priority could be trivial?

2. ANW-276

   1. probably not - not sure how complex it would be

   2. still a major usability issue

3. ANW-275

   1. probably not - not sure how complex it would be

   2. priority major, could be minor, but is an annoying issue

4. ANW-288

   1. looks like it’s done. close ticket?

5. ANW-345

   1. already closed. great!

6. ANW-292

   1. probably not, sounds complicated

7. ANW-316

   1. not sure

   2. didn’t have time to check if this was still an issue but was noted recently

8. ANW-308

   1. not sure

   2. priority major, maybe could be minor?

Julia Lydia

1. ANW-323

   1. y/n

   2. other concernsthis is a catchcall for issues on a theme. Most of those issues are resolved and the rest are in ready for implementation. Close this ticket?

2. ANW-604

   1. seems to be resolved. Close?

3. ANW-425

   1. no? Perhaps too complex

   2. major priority, major UX/accessibility issue

4. ANW-635

   1. need to investigate more

5. ANW-652

   1. it seems like improvement has been done but that it didn’t help Cory’s particular issue. Should we close this and ask him to file a new ticket?

6. ANW-664

   1. need to investigate more

7. ANW-665

   1. maybe? It could be a simple fix, but I’m not sure how complicated it would be.

8. ANW-691

   1. need to investigate more

Reviewing Ready for Development tickets: Feature request kanban board (65 tickets)

William

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-616

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-215

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-453

4. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-468

5. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-332

6. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-340

7. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-534

8. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-528

Edgar

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-400

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-386

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-330

4. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-540

5. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-455

6. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-490

7. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-473

8. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-539

Terra

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-532

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-550

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-517

4. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-443

5. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-462

6. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-445

7. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-442

8. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-489

Lydia

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-214

   1. no - not for a community developer

   2. is there enough info. What should an unpublished archival object look like?

   3. Priority is ok at low.

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-538

   1. no - not for a community developer - I don’t know if a community developer would know how to do this.

   2. a nice usability feature

   3. priority is low because of existing workarounds

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-349

   1. possibly, but I don’t know if a community developer would know how to do this

   2. a nice usability feature

   3. priority is low and could be trivial instead

4. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-97

   1. no - not for a community developer - I don’t know if a community developer would know how to do this, particularly if it automatically strips permissions (which would be helpful)

   2. a nice usability feature

   3. priority minor ok

5. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-553

   1. no - not for a community developer, it sounds like the datepicker currently used is part of a larger discussion

   2. a nice usability feature

   3. priority minor ok

6. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-348

   1. no - sounds complex

   2. a nice usability feature

   3. priority minor ok

7. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-559

   1. no - this involves some architecture planning that probably the program team only knows

   2. a nice usability feature

   3. priority minor ok

8. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-564

   1. Close this ticket. This ticket was in response to an older method of reorder. I can’t currently think of another pressing need for an “undo” function.

Patrick

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-352

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-207

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-561

4. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-210

5. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-384

6. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-329

7. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-253

8. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-280

9. ANW-352

   1. Yes

   2. Just moving the location of the revision statement notes

10. ANW-207

    1. No

    2. As of Feb. 2018 we said we needed more information about the size/scope of the work

11. ANW-561

    1. No

    2. Too large of scope and already part of Staff Interface working group specs

12. ANW-210

    1. Yes

    2. Seems to be just pulling some data into a form.

13. ANW-384

    1. Yes

    2. However, don’t know how intricate RDE work is.

14. ANW-329

    1. Yes

    2. Would also need to update Repository preferences to add this as an allowable column

15. ANW-253

    1. Yes

    2. I think there are some questions about whether this is a unique issue though

16. ANW-280

    1. Yes

Julia

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-255

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-256

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-277

4. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-273

5. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-615

6. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-601

7. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-638

8. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-658

Alicia

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-661

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-662

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-663

4. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-681

5. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-685

6. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-685

7. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-725

8. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-730

Extras (Lydia took them)

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-738

   1. no - too complex for community dev.

   2. worthwhile project - is spec ok?

   3. minor priority seems ok

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-759

   1. no - too complex for community dev.

   2. worthwhile project - is spec ok?

   3. minor priority seems ok

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-808

   1. unsure if this is still an issue, could possibly close?

4. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-799

   1. no - unsure if community developers would have access to this security area, otherwise seems relatively straightforward to find the right code to fix.

5. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-806

   1. maybe? It sounds like an HM plugin for adapting the Staff Interface might be able to be copied to the PUI, but I don’t know if it’s that easy.

6. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-809

   1. no? not sure how complex it would be to fix

   2. priority of major is good because of accessibility being protected by law.

7. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-816

   1. no? not sure how complex it would be to fix

8. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-843

   1. no? not sure how complex it would be to fix

   2. priority major, not sure it should be minor, but it would be a helpful function

9. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-908

   1. maybe? I’m not sure how difficult it would be to copy code from the Resource record template and also map the data when it is spawned into a Resource.

   2. priority minor seems ok