No edit summary
clarification clean up
Line 1: Line 1:
==Getting Rid of Headlines==
==Deprecate the Headlines Parameter on This Template==
As I was adding headlines to the affected characters from issue #1, it felt redundant now that it shows up on the timeline. Especially when it describes itself as a headline. I have no problem with getting rid of this and the parameter here in the infobox template.
As I was adding headlines to the affected characters from issue #1, it felt redundant now that it shows up on the timeline. Especially when it describes itself as a headline. I have no problem with getting rid of this and the parameter here in the infobox template.
--[[User:Astrozac|Astrozac]] ([[User talk:Astrozac|talk]]) 23:07, 5 June 2016 (PDT)
--[[User:Astrozac|Astrozac]] ([[User talk:Astrozac|talk]]) 23:07, 5 June 2016 (PDT)
Line 5: Line 5:
:Besides Headlines, there are lots of things that can be generated from the Event Annotations/Timelines data.  The trick is getting enough events annotated and entered so that we can make the switch-over without too much if any data loss.   
:Besides Headlines, there are lots of things that can be generated from the Event Annotations/Timelines data.  The trick is getting enough events annotated and entered so that we can make the switch-over without too much if any data loss.   


:I suggest not hand entering Headlines into the individual character pages going forward, as we do seem to have a decent amount of them as event/annotations (although many of them need to be more fully detailed).  Instead build the actual event entry and let Symantic Wiki do the mundane data entry.  I do plan to build a query that will pull the headlines out of the generic event list, as I think it is nice to see that data without navigating through a long compilation of data.
:I suggest not hand entering Headlines into the individual character pages going forward, as we do seem to have a decent amount of them as event/annotations (although many of them need to be more fully detailed).  Instead build the actual event entry and let Semantic Wiki do the mundane data entry.  I do plan to build a query that will pull the headlines out of the generic event list, as I think it is nice to see that data without navigating through a long compilation of data.


:Appearances for this template will also be shifted to a query in the future, again once there is a more reasonable amount of event/annotations in play.  Anyone can continue hand editing appearance at their discretion, or spend the time building the event.  It's up to them.  But realize, somewhere in the future, appearance lists will be automated.  Long time future given our current pace at building events. --[[User:Infobroker|Infobroker]] ([[User talk:Infobroker|talk]]) 14:20, 6 June 2016 (PDT)
:Appearances for this template will also be shifted to a query in the future, again once there is a more reasonable amount of event/annotations in play.  Anyone can continue hand editing appearance at their discretion, or spend the time building the event.  It's up to them.  But realize, somewhere in the future, appearance lists will be automated.  Long time future given our current pace at building events. --[[User:Infobroker|Infobroker]] ([[User talk:Infobroker|talk]]) 14:20, 6 June 2016 (PDT)
Line 30: Line 30:
:* Fireman Arnold Prentice Loses His Leg in a Rescue Operation
:* Fireman Arnold Prentice Loses His Leg in a Rescue Operation


:I may not have provided the best titles for the events, but the event titles themselves have strong context about the event, and they don't get overly granular in scope.  You can certainly break them into a set of tinier events.  The second event in the list for example, could be listed as:  the visit to the fire station, the ride in the car and the stop at the cemetery.  But it would be overly minute and a bit anal.  The goal should be identify as large a glob of an event as possible, graph it to a period of time on the timeline, and then go into the details of the characters and devices that are present at the event. Winged Victory would get listed in the event as a character "element" with maybe a summary bullet mentioning she was flying over Broome Campus.  
:I may not have provided the best titles for the events, but the event titles themselves have strong context about the event, and they don't get overly granular in scope.  You can certainly break them into a set of tinier events.  The second event in the list for example, could be listed as:  the visit to the fire station, the ride in the car and the stop at the cemetery.  But it would be overly minute and a bit anal.  The goal should be to 1)identify as large a scope of an event as possible, 2)graph it to a period of time on the timeline, and then 3)go into the details of the characters and devices that are present at the event. Winged Victory would get listed in the second listed event as a character "element" with maybe an added summary bullet mentioning she was flying over Broome Campus.  


:I typed up a longish note to myself a long time ago, pre-Herocopia, when I was doing annotations locally in a database system on one of my computers.  It detailed what constitutes an event.  A couple years back, that turned into a letter. Segments of the letter were used in the early help pages for events, but not much of the "what constitutes" part made it here.  Maybe now that there are enough examples out there, I should find a place for it somewhere on the help pages.  --[[User:Infobroker|Infobroker]] ([[User talk:Infobroker|talk]]) 14:20, 10 June 2016 (PDT)
:I typed up a longish note to myself a long time ago, pre-Herocopia, when I was doing annotations locally in a database system on one of my computers.  It detailed what constitutes an event.  A couple years back, that turned into a letter. Segments of the letter were used in the early help pages for events, but not much of the "what constitutes" part made it here.  Maybe now that there are enough examples out there, I should find a place for it somewhere on the help pages.  --[[User:Infobroker|Infobroker]] ([[User talk:Infobroker|talk]]) 14:20, 10 June 2016 (PDT)