<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Ah, and let's not forget (as far as
upgrade-friendly customisation is concerned) the custom subjects,
divisions and phrases.<br>
<br>
On 20/07/2015 12:10 μμ, George Mamalakis wrote:<br>
</div>
<blockquote
cite="mid:EMEW3|a318c9e1b5692425de1faa0de91b0038r6JACB14eprints-tech-bounces|ecs.soton.ac.uk|55ACBB09.7070906@eng.auth.gr"
type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Adam,<br>
<br>
Given recent developments (the divisions-and-subject bug), soon
I'll need to upgrade my repository (or just patch it, but I
prefer upgrading). The current EPrints documentation (<a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://wiki.eprints.org/w/Upgrading_EPrints_3_versions">http://wiki.eprints.org/w/Upgrading_EPrints_3_versions</a>)
is clearly not adequate for an upgrade to anyone having
customised even the slightest bit of EPrints. What I would do in
order to upgrade would be to backup my ~eprints directory,
upgrade my EPrints package using debian's apt-get, upgrade my
EPrints installation using ~eprints/bin/epadmin upgrade (hoping
that this would not change anything in live my repository, but
I'm relatively optimistic that it won't), create a new
repository with the latest version, and follow my extensive
guidelines from my redmine issues to bring the new repository to
the same state as my previous one.<br>
<br>
This method may work for me, but I don't think that this is what
an EPrints newcomer would expect to do when upgrading their's.
So -and based on my current experience with EPrints- I think
that two -or more videos- (or any other means of documentation)
need to be available for EPrints maintenance:<br>
<br>
- a few videos explaining how to *CORRECTLY* customise an
EPrints repository, by adding new configuration files or
whatever is needed to be changed, without touching anything that
an upgrade would break (like custom workflows, custom plugins,
branding (xhtml pages and css), custom fields, custom searches,
and practically *EVERYTHING* that usually people wish to change
-and are afraid doing- after installing EPrints). What I've
understood so far from my small experience with EPrints, and
please correct me if I'm wrong, is that the "cleanest" way of
customising anything in EPrints would be to not change any
vanilla files, create new files that "override" EPrints' default
"behaviour" and finally (maybe optionally, but not sure) create
a bazaar package (for
portability/installation-independence/decoupling/maintenance). I
am not sure, though (architecturally speaking), if every
customisation can be achieved without tainting the initial
installation, and If so, the package step is then mandatory.<br>
<br>
- a smaller video showing how to upgrade EPrints from one
version to another, that also shows how customisations haven't
been affected, or how they have been addressed using the
previously generated packages.<br>
<br>
I know that you've made two great videos regarding bazaar
packages (I've only watched one of them, and will watch the
second after I finish my customisations and start creating
packages for each feature I had to add), but I'm sure that
novices (like me) would like to know many more details wrt to
packages in regard to each type of EPrints customisation
(branding, workflows, custom fields/searches, etc).<br>
<br>
Unfortunately, current EPrints documentation is very
distributed, sometimes deprecated and worst of all: *not upgrade
friendly at all*. If I follow the steps I've read in EPrints
documentation for my customisations, there would be no way my
repository would function after following the documentation's
upgrade procedure. And clean upgrade procedures is a *MUST* in
any software product.<br>
<br>
Thanks again Adam, and all of you, for all the help, and once I
finish with my repo I'll update EPrints wiki (since I'm more of
a reading type rather than a watching one :)) with all my
notes, because at the moment, a newcomer would not be able to do
things "right" just by following it and not asking this list.<br>
<br>
On 20/07/2015 05:05 πμ, Adam Field wrote:<br>
</div>
<blockquote
cite="mid:EMEW3|e412445e107a1bdbdfabd05300974b44r6J35B05af05v|ecs.soton.ac.uk|121DC5C7-8653-4AD1-87BF-84453776EC80@ecs.soton.ac.uk"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
I've added some of your suggestions to my list of video idea.
Browse View configuration and the EPrints workflow are already
already on my list, but I've added search configuration and user
roles, too.
<div><br>
</div>
<div>Is there anything you're working on at the moment that a
video would help with?<br>
<div>
<div><br>
<div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows:
auto; word-spacing: 0px; -webkit-text-stroke-width:
0px; word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;">
<div>--<br>
Adam Field<br>
Business Relationship Manager and Community Lead<br>
EPrints Services</div>
<div><br>
</div>
<div>I am currently not working in the UK. Due to
timezone differences (GMT -9) email responses may
take longer.</div>
</div>
</div>
<br>
<div>
<div>On 16 Jul 2015, at 14:51, <a
moz-do-not-send="true"
href="mailto:mamalos@eng.auth.gr">mamalos@eng.auth.gr</a>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;">
<div style="font-size:10pt;">
<div style="margin-top: 0px; margin-bottom: 0px;">Maybe
a small video explaining custom browse-by
alternatives and adding them to the menu? Or how
to add newly created fields in searches maybe
(since you have lots of videos that add new
fields)? Or how to configure workflows (user,
eprints, etc) and maybe how to create a package
with the new workflows. Ah, or how about adding
new user groups and explain how roles, etc work?</div>
<p style="margin-top:0;margin-bottom:0;"> </p>
<div style="margin-top: 0px; margin-bottom: 0px;">Ok,
now I stop, I think that's enough suggestions
from one person:-) :-) .</div>
<p style="margin-top:0;margin-bottom:0;"> </p>
<div style="margin-top: 0px; margin-bottom: 0px;">------
Αρχικό μήνυμα------</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><b>Από: </b>Adam
Field</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><b>Ημερομηνία: </b>Τετ,
15 Ιουλ 2015 11:22</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><b>Προς: </b><a
moz-do-not-send="true"
href="mailto:eprints-tech@ecs.soton.ac.uk">eprints-tech@ecs.soton.ac.uk</a>;</div>
<div style="margin-top: 0px; margin-bottom: 0px;"><b>Θέμα:</b>[EP-tech]
Automatic Fields training video</div>
<p style="margin-top:0;margin-bottom:0;"> </p>
With today's publication of the Automatic Fields
training video at <a moz-do-not-send="true"
href="https://youtu.be/17OuthpCxck">https://youtu.be/17OuthpCxck</a>
(and <a moz-do-not-send="true"
href="http://wiki.eprints.org/w/Training_Video:Automatic_Fields">http://wiki.eprints.org/w/Training_Video:Automatic_Fields</a> ),
I've completed my trilogy covering the
configuration of default, virtual and automatic
fields.
<div><br>
</div>
<div>If anyone watches it and finds it useful, I'd
be grateful if they would supply me with an
index to include on the youtube page, in the
form of:</div>
<div><br>
</div>
<div>0:00 Introduction</div>
<div>0:30 Topic 1</div>
<div>1:43 Topic 2</div>
<div>4:37 Topic 3</div>
<div>...etc</div>
<div><br>
</div>
<div>Also, does anyone have any requests for the
next video? I'll give preference to less
technical topics as the last few videos have
been perl-heavy.</div>
<div><br>
<div apple-content-edited="true">
<div style="letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;">
<div>--<br>
Adam Field<br>
Business Relationship Manager and
Community Lead<br>
EPrints Services</div>
<div><br>
</div>
<div>I am currently not working in the UK.
Due to timezone differences (GMT -9)
email responses may take longer.</div>
</div>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
George Mamalakis
IT and Security Officer,
Electrical and Computer Engineer (Aristotle Univ. of Thessaloniki),
PhD (Aristotle Univ. of Thessaloniki),
MSc (Imperial College of London)
School of Electrical and Computer Engineering
Aristotle University of Thessaloniki
phone number : +30 (2310) 994379
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">*** Options: <a class="moz-txt-link-freetext" href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a>
*** Archive: <a class="moz-txt-link-freetext" href="http://www.eprints.org/tech.php/">http://www.eprints.org/tech.php/</a>
*** EPrints community wiki: <a class="moz-txt-link-freetext" href="http://wiki.eprints.org/">http://wiki.eprints.org/</a>
*** EPrints developers Forum: <a class="moz-txt-link-freetext" href="http://forum.eprints.org/">http://forum.eprints.org/</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
George Mamalakis
IT and Security Officer,
Electrical and Computer Engineer (Aristotle Univ. of Thessaloniki),
PhD (Aristotle Univ. of Thessaloniki),
MSc (Imperial College of London)
School of Electrical and Computer Engineering
Aristotle University of Thessaloniki
phone number : +30 (2310) 994379
</pre>
</body>
</html>