maiers / aigaion Goto Github PK

The website aigaion.de, which the Sourceforge project page links to, is effectively down with an HTTP error 403 Forbidden. Anything you can do about it?

This is not working at all in 2.5 for me. When I try to log in with a new user, and login with that new user, I get an empty page returned for /index.php/publications. I set up the user with the exact same priviliges and settings as the admin account, to see if it was an error there, but that did not fix the problem.

Two fields N2 and AB are in wrong order in the array $risElements in file parseentries_ris.php

Commit 33d8be7 solves this issue.

An index could be added so that author_db.php->getByExactName() query would run much quicker.

ALTER TABLE .author DROP INDEX surname ,
ADD INDEX exactname ( surname ( 10 ) , firstname ( 10 ) , von ( 5 ) , jr ( 5 ) )

This Issue is part of an attempt to optimize importing into a big Aigaion database (currently 10,000+ authors, 80,000+ publications). Our installed Aigaion seems to crash or time-out when importing datasets with more than 300 publications.

Hi,

I noticed that aigaion.de hasn't be accessible in a while (Forbidden : You don't have permission to access ...).

Just a heads up !

For database optimization, both columns 'keyword' and 'cleankeyword' could be changed to type VARCHAR(255). RIS standard allows up to 255 character for a keyword (http://www.refman.com/support/risformat_intro.asp).

The advance search area triggers the following PHP-notice:

A PHP Error was encountered

Severity: Notice

Message: Topic_db::getFromRow(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "User" of the object you are trying to operate on was loaded before unserialize() gets called or provide a __autoload() function to load the class definition

Filename: libraries/topic_db.php

Line Number: 106

Hi,

I just downloaded the master and attempted to run it. I can't seem to add users other than the admin at all. (I was using the 2.2beta but the php messages made it difficult to use it.) It's a fresh install. I created a new database and set it up from scratch.

Thanks,
Ankur

Our Aigaion database now holds 10,000+ authors and 80,000+ publications (these values are will grow to double their size when importing new data has been fullfilled).

When importing more than 300 entries (or more than 900 entries with index added as explained in issue #8) the importing stops and loads an empty white page.

When looking at the mysql processlist during import, it seems that the most time consuming query is the data transfer for refreshBibtexIdLinks(). This function is called for every added publication, and must send all the pub_id and bibtex_id from the mysql database over to php (that is 2*80,000+ values in our case). I am not yet sure what the purpose of this function is, but it doesn't seem to affect the database, only keeps all the values in the user's CI session.

Could someone explain what this function does?

Hi, I am hosting a fork from oschwede repo of aigaion. I tried to create the aigaion organization on github to host the project but it already exists. Are you the owner of the organization or do you know who is? I want to revive this project an seems that this organization is the best place to host this project. The aigaion organization was created in 2015 an there is no public project released.

Hi, I have forked this project and wish to know if you are still interested on it. I want to keep the project alive updating and implementing new features.

Aigaion keeps every publication's pub_id and bibtex_id stored in a session cache variable for later crossreferencing needs (helpers/bibtex.php). Instead of keeping everything in a cached variable, it would be better to use database queries.

For memory it would be better, because the bigger your database is, the more memory it will require (and reach PHP's memory_limit, by default 128 MiB).

For performance it would be much better, because there would be no need for looping through all the tens of thousands of publication rows stored in Aigaion (nor to send this data between MySQL and PHP) every time any single publication is added/updated/deleted.