Difference between revisions of "BP revision ticket triage"

From TEIWiki
Jump to navigation Jump to search
(easy implementation: updated statuses)
(medium implementation)
Line 21: Line 21:
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] – complete
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] – complete
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/18 issue 18: rework Level 1 and Level 2 structure?] – decided not to implement
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/18 issue 18: rework Level 1 and Level 2 structure?] – decided not to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/24 issue 24: tagging events] – In May 2016 meeting we felt that we should leave to Council to implement in P5 first, but subsequent discussion on the ticket questions this. Andrew will try to dig up some past discussion of event tagging to share for consideration.
+
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/24 issue 24: tagging events] – Andrew will investigate
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/25 issue 25: Cover MARC records and TEI body] – BPTL group think this is out of scope. Since Stuart hasn't added anything, we've closed the issue.
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/25 issue 25: Cover MARC records and TEI body] – BPTL group think this is out of scope. Since Stuart hasn't added anything, we've closed the issue.
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/42 issue 42: idno as child of biblStruct]
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/42 issue 42: idno as child of biblStruct]

Revision as of 19:15, 12 September 2016

Probably not controversial

easy implementation

medium implementation

hard implementation

Could be controversial

easy implementation

medium implementation

hard implementation

Postpone