I knew about that. Thought I'd saved it published (since it is in development after all) but I don't see my changes anymore. :(<br clear="all"><div><br></div>
<br><br><div class="gmail_quote">On Fri, Oct 5, 2012 at 1:00 PM, Jim Craner <span dir="ltr"><<a href="mailto:jim@galecia.com" target="_blank">jim@galecia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div bgcolor="#ffffff" text="#000000">
Well, we can have revision control on, I think it actually is
already but if you haven't saved the doc once, then Drupal won't
know it exists. <br>
<br>
If you want to create something as a draft, just create it and save
it but uncheck the "Published" box before doing so. When you're
ready for it to be visible to the public, edit it, check the
"Published" box, and save it, and it will then "go live" instantly.<br>
<br>
Let me know if this is clear.<br>
<br>
Thanks!<span class="HOEnZb"><font color="#888888"><br>
Jim</font></span><div><div class="h5"><br>
<br>
On 10/05/2012 10:01 AM, Lori Bowen Ayre wrote:
<blockquote type="cite">I did a little working on editing the Community page.
Or so I thought. I don't see it now. I wonder if I failed to
save my work....Does Drupal keep drafts?
<div><br>
</div>
<div>Lori<br>
<div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
On Fri, Oct 5, 2012 at 7:24 AM, Steve Wills <span dir="ltr"><<a href="mailto:swills@beyond-print.com" target="_blank">swills@beyond-print.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thank you Alexey.<br>
<br>
Since the meeting I think we decided to "stay in touch" but
not schedule another conference call at this time? I also
agreed to send out a cheerleading email toward the end of
this week. Here it is.<br>
<br>
I am pleased to announce that I have another public school
system *almost* running on Evergreen but between my fulltime
day job and the ILS migrations for that school system, I
have not had a change to review the content issues for the
new Drupal site. I also want to work on the map
functionality but, again, have made no progress.<br>
<br>
How is everyone else doing?<br>
Steve Wills<br>
<div> </div>
<blockquote style="padding-left:5px;margin-left:5px;border-left:2px solid rgb(0,0,255);margin-right:0px"><font face="Tahoma">-----Original Message-----<br>
<b>From:</b> Lazar, Alexey Vladimirovich [mailto:<a href="mailto:alexey.lazar@mnsu.edu" target="_blank">alexey.lazar@mnsu.edu</a>]<br>
<b>Sent:</b> Friday, October 5, 2012 09:43 AM<br>
<b>To:</b> 'Evergreen Community Web Team Email List'<br>
<b>Subject:</b> [Evergreen-web-team] 2012-08-30 EG Web
Team meeting notes<br>
<br>
</font>Evergreen Web Team meeting notes
Date: 2012-08-30
Type: conference call
Next meeting: 2012-09-13 at 14:30 ET | 13:30 CT | 12:30 MT
| 11:30 PT (USA)
Attendees:
* Anoop Atre * Lori Bowen Ayre (notetaker)
* Jim Craner * Alexey Lazar (notetaker)
* Benjamin Shum * Stephen Wills Done:
* Jim: Evergreen logo and footer added to the prototype
website (content)
* Jim: created an editor field on each page to identify
who is responsible for what part of content. All the
editors will be listed at the bottom of each page. We
don't expect the editor lists to get too long, but if this
approach becomes a problem, we'll deal with it then.
(content management)
Topics that were discussed:
* Review past todo items, mark as done, plan next steps
* Planning for the web Team report for the community
meeting on September 14, 2012.
* Time zones. Most people preferred to use US Eastern time
as the default time zone for the public side of the new
website, although users can choose their own preferences
when they log in.
* "Group" pages in Drupal, which behave differently than
normal content pages, may be useful for certain situation
such as Oversight Board, DIG, task forces. We need to
explore the functionality available and talk with the
various groups. * Blogs: We need to discuss/review
blogging feature with current bloggers. * Calendars: We
need to discuss Drupal calendar features/options with
current calendar owners. Identify potential candidates for
Drupal role of Event manager(s).
* Evergreen map and directory functionality: interest in
continuing to document Evergreen libraries, but this feels
like a big project and it needs someone to manage it.
New to-do items:
* Jim and Alexey to prepare the report for the September
14, 2012 community meeting.
Old to-do items:
* Alexey: start working on Web Team content (content
migration)
* Jim: will look at options for adding a left-menu
* Alexey: send out a call for anyone interested to get
involved in prototyping of blog, calendar and
maps/directory functionality
On the radar (these topics were mentioned):
* Review current official and unofficial pages for content
migration needs
* Future conference website (2014)
--
Alexey Lazar
PALS
Information System Developer and Integrator
<a href="tel:507-389-2907" value="+15073892907" target="_blank">507-389-2907</a>
<a href="http://www.mnpals.org/" target="_blank">http://www.mnpals.org/</a>
_______________________________________________
Evergreen-web-team mailing list
<a href="mailto:Evergreen-web-team@list.evergreen-ils.org" target="_blank">Evergreen-web-team@list.evergreen-ils.org</a>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a>
</blockquote>
<br>
Evergreen Web Team meeting notes<br>
<br>
Date: 2012-08-30<br>
Type: conference call<br>
Next meeting: 2012-09-13 at 14:30 ET | 13:30 CT | 12:30 MT |
11:30 PT (USA)<br>
<br>
Attendees:<br>
* Anoop Atre <<a href="mailto:aatre@esilibrary.com" target="_blank">aatre@esilibrary.com</a>><br>
* Lori Bowen Ayre <<a href="mailto:lori.ayre@galecia.com" target="_blank">lori.ayre@galecia.com</a>>
(notetaker)<br>
* Jim Craner <<a href="mailto:jim@galecia.com" target="_blank">jim@galecia.com</a>><br>
* Alexey Lazar <<a href="mailto:alexey.lazar@mnsu.edu" target="_blank">alexey.lazar@mnsu.edu</a>>
(notetaker)<br>
* Benjamin Shum <<a href="mailto:bshum@biblio.org" target="_blank">bshum@biblio.org</a>><br>
* Stephen Wills <<a href="mailto:swills@beyond-print.com" target="_blank">swills@beyond-print.com</a>><br>
<br>
Done:<br>
* Jim: Evergreen logo and footer added to the prototype
website (content)<br>
* Jim: created an editor field on each page to identify who
is responsible for what part of content. All the editors
will be listed at the bottom of each page. We don't expect
the editor lists to get too long, but if this approach
becomes a problem, we'll deal with it then. (content
management)<br>
<br>
Topics that were discussed:<br>
* Review past todo items, mark as done, plan next steps<br>
* Planning for the web Team report for the community meeting
on September 14, 2012.<br>
* Time zones. Most people preferred to use US Eastern time
as the default time zone for the public side of the new
website, although users can choose their own preferences
when they log in.<br>
* "Group" pages in Drupal, which behave differently than
normal content pages, may be useful for certain situation
such as Oversight Board, DIG, task forces. We need to
explore the functionality available and talk with the
various groups.<br>
* Blogs: We need to discuss/review blogging feature with
current bloggers.<br>
* Calendars: We need to discuss Drupal calendar
features/options with current calendar owners. Identify
potential candidates for Drupal role of Event manager(s).<br>
* Evergreen map and directory functionality: interest in
continuing to document Evergreen libraries, but this feels
like a big project and it needs someone to manage it.<br>
<br>
New to-do items:<br>
* Jim and Alexey to prepare the report for the September 14,
2012 community meeting.<br>
<br>
Old to-do items:<br>
* Alexey: start working on Web Team content (content
migration)<br>
* Jim: will look at options for adding a left-menu<br>
* Alexey: send out a call for anyone interested to get
involved in prototyping of blog, calendar and maps/directory
functionality<br>
<br>
On the radar (these topics were mentioned):<br>
* Review current official and unofficial pages for content
migration needs<br>
* Future conference website (2014)<br>
<br>
--<br>
<br>
Alexey Lazar<br>
PALS<br>
Information System Developer and Integrator<br>
<a href="tel:507-389-2907" value="+15073892907" target="_blank">507-389-2907</a><br>
<a href="http://www.mnpals.org/" target="_blank">http://www.mnpals.org/</a><br>
<br>
_______________________________________________<br>
Evergreen-web-team mailing list<br>
<a href="mailto:Evergreen-web-team@list.evergreen-ils.org" target="_blank">Evergreen-web-team@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
<br>
<br>
_______________________________________________<br>
Evergreen-web-team mailing list<br>
<a href="mailto:Evergreen-web-team@list.evergreen-ils.org" target="_blank">Evergreen-web-team@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<pre><fieldset></fieldset>
_______________________________________________
Evergreen-web-team mailing list
<a href="mailto:Evergreen-web-team@list.evergreen-ils.org" target="_blank">Evergreen-web-team@list.evergreen-ils.org</a>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Evergreen-web-team mailing list<br>
<a href="mailto:Evergreen-web-team@list.evergreen-ils.org">Evergreen-web-team@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-web-team</a><br>
<br></blockquote></div><br>