the alternative could be that we just an appropriately sized maxlength on all the default fields in eprints_fields.pl
But URIs are a valid way of doing it, and they can get a bit lengthy
The issue i have now is that ive been round eprints.soton putting limits on all my set fields
but i have to work out a slick way to generate script which generates alter statements to change my database to fit.
ive got dev pre-prod and prod so there is plenty of sandpits to play in
I suppose it really depends if it's a housekeeping issue at soton - then you could probably get something to work out what the maximum length of your sets are, and set that as a max. And there are some fields that could almost certainly have 20 or less and no-one would notice
But if it's global, then I think it needs to be a bit more lenient
like everything will start up happily and looks like it works
and when you come to submit to the workflow you get a 500 and all the data from that form stage gets blow away...
that bug probably exists already but no one has ever written a test to see what happens if you make key which is over 255 long.
there should probably be some proper validation for that and a graceful failure case....
for added brownie points it could do the same check to decide an approrpiately sized varchar
hmm it appears gitter is shit
it keeps dropping my messages
the downside of that approach is adding an item to named set will sometimes involve calling "epadmin update" which maybe undesirable
If you don't add it to the options in the workflow, you can't retain a value in that field = data loss when someone edits the EPrint. I'm currently wrestling this for a licence field that does more sensible things than the current one!
At least that's what was happening on our 3.3.10 server!
can you not just add e to the set?
does that mean you can do $eprint->set_value("yourset", "e"); it just lets you do that?
because if so thats a bit cheesy isnt it
or are you putting values directly in the database?
It's useful to be able to store values that aren't defined - maybe a flag on a named set - 'constrain_to_known_values' - but by default, if you've stored a value X, it shouldn't get silently thrown away!
It would need an option in the form which says "Retain current value"
Yep - this is exactly what I'm thinking for a new 'Licence' type field - have a default set of e.g. v4 CC licenses (plus a few others), but allow someone to store a URI to any licencse. By default it would allow a saved, but unknown value to be retained. An admin function would also allow an easy way to find 'unknown values' - so instead of rendering them as e.g. just a URI, you can add a phrase for the URI - and render it in a more friendly way!
Hey guys, I'm not sure if you can help me: I want to configure my eprints repo to access the same archive using two domains. I think this should be done with the {aliases} option in .../myrepo/cfg/cfg.d/10core.pl and reloading all documents with generate* in eprints3/bin. But this don't work for me: I can access the repo with both domains, but it is just the same as an redirect in the apache config. All links on the page are hardlinks that point to the first domain so the second domain is not usable. Do you have any suggestions? I already asked at eprints-tech mailing list, but they can't help me. Thank you very much for your help!
I've seen it there (and here, too, now) but haven't been able to invest much thought into it. In the past we've had a similar-but-different issue, where I wanted to configured our repo to be HTTPS-by-default (but still allow some endpoints to be accessible under cleartext HTTP). I never really resolved that properly.
Hey @zstoynova, unfortunately, I was not able to solve it. I created a very ugly workaround: two Apache vhost-configs with the same eprints ID and different domains, one of them using mod_substitute to change all links to its domain. The second vhost with the 'false' domain includes this additional lines:
<Location "/">
AddOutputFilterByType INFLATE;SUBSTITUTE;DEFLATE text/html text/plain text/cgi
Substitute "s;http://example.com;http://example2.com;ni"
</Location>
while example.com is the domain known to eprints and example2.com is the additional domain name.
with a very small user group. Our library team needs two different domains for cooperation with publishing companies.
We would like use git for the development of the Eprints archives. therefore we have a production and a test server for the master and develop branch versions of our repository. Actually our production archives are in fact duplicated on the test server and we would like to access them using <archivename>-test ..... we thought that using an alias with no redirection will solve our problem but the as it was alreaydy explaine all links on the page are hardlinks that point to our production domain so our test domain is not usable.
Hi @Rotatabol we have tested your solution and everything works except user login. It seems that the original domain address is given as an argument "rel_cgipath" to login redirection address and therefore apache configuration with mod_substitute plays no role. Did you have similar problem or not?