status 'published'

[Paul Osseweijer]

Hello,

I was able to import 600 archival descriptions (via a XML-import) from
out current system to ICA-AtoM. When imported all descriptions have
the Publication Status 'Draft'. Is there a way to set all descriptions
to 'Published'. To do this by hand for 600 descriptions is not a nice
job.

Paul

[Evelyn McLellan]

Hi Paul,

Agreed, this would be quite the time-consuming task. I'll see if
there's a better way you can publish the descriptions and get back to
you soon.

Evelyn McLellan
ICA-AtoM Community Manager

[David Juhasz]

Hi Paul,

You can update the publication status of all of your information
objects:

1) First backup your SQL database. If you are using MySQL you can do
this from the command line with the command:

"mysqldump -u {username} -p -h {hostname} {database_name} > backup.sql"

2) Update the publication status with the SQL query (published = 160,
draft = 159):

"UPDATE q_status SET status_id = 160 WHERE status_id = 159;"

3) Update your search index, once again from the command line type:

"php /path/to/ica-atom/symfony search:populate QubitSearch"

That should do the trick. Let me know if you have any problems.

David Juhasz,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | P: 604.527.2056 | F: 604.521.2059

[Paul Osseweijer]

Hi David,

Thanks for your reply. I did the things you described but the
publication status was not changed, it is still on 'draft' for the new
imported archival descriptions.

When I executed the SQL-query only one row was updated, I expected 600
should be updated. The table q_status contains only 133 rows. When I
set the publication status in ICA-AtoM to 'published', I see there is
a new row added to the table q_status. What can I do to solve this?

Best regards,
Paul

[David Juhasz]

Hi Paul,

Ahhh, now I see. A status record for each archival description should
be created on import, but there is a bug in Release 1.0.9; I've created
a new issue [1] for this bug.

[1] => http://code.google.com/p/qubit-toolkit/issues/detail?id=1658

You can use MySQL to create the missing status records (and publish the
descriptions), but it's a complex query, so please make sure to *backup
your data* before running the following MySQL command:

"INSERT INTO q_status (object_id, type_id, status_id) SELECT
q_information_object.id, 158, 160 FROM q_information_object LEFT JOIN
q_status ON q_information_object.id = q_status.object_id WHERE
q_information_object.id > 1 AND q_status.id is null;"

After running this query, you will need to rebuild your search index
again to sync it with the publication status data.

Let me know if you have any problems.

Regards,

--

David Juhasz,
Software Engineer, Artefactual Systems Inc.

http://www.artefactual.com | P: +1.604.527.2056 | F: +1.604.521.2059

[Paul Osseweijer]

Hi David,

Yes, the new query did the trick: all descriptions are now published.
Thanks for your help.

I only have problems running the command for rebuilding the search
index,
after some time it ends with: Segmentation fault. I think i had this
problem allready before.

I see in the discussiongroup this a kown issue. It tried to pinpoint
the record where the indexprocess stops, delete the next record, but
did'not solve the problem. How could I solve this?

Regards, Paul

[David Juhasz]

Hi Paul,

We've been wrestling with the segmentation fault problem for a while
unfortunately, as you can see from the bug report [1]. Probably your
best bet to work around the issue is a patch that my colleague Jesús
Garcia Crespo has created which allows restarting the indexing process
after a segmentation fault. I've cc'd Jesús on this email, and I'm
sure he'll respond in the next day or two (he's located in Spain so it's
quite late in his local timezone right now).

[1] => http://code.google.com/p/qubit-toolkit/issues/detail?id=1128

[Paul Osseweijer]

Hi David,

I solved the problem by deleting the empty records in the table
q_information_object_i18n, there were 6 six almost empty records.
After that the indexprocess completed succesfully.

Regards, Paul

[David Juhasz]

Hi Paul,

Wow, it's very interesting that clearing empty records helped the
segfault problem. Thanks for the feedback, it may be helpful for
eventually fixing the problem.

Regards,

David Juhasz,
Software Engineer, Artefactual Systems Inc.

http://www.artefactual.com | P: 604.527.2056 | F: 604.521.2059

[Jesús García Crespo]

Hi Paul,

Sorry for my late response.

On Fri, Sep 10, 2010 at 4:40 PM, Paul Osseweijer <poss...@gmail.com> wrote:

I solved the problem by deleting the empty records in the table
q_information_object_i18n, there were 6 six almost empty records.
After that the indexprocess completed succesfully.

Nice one, I'll see if this solution is applicable in any case. Thank you.

Next time you can't get rid of a segfault during the index build process, please feeel free to try this patch: http://www.sevein.com/tmp/icaatom109-segfault-populate.patch in order to restart the process from the point you tell as command line options (ioOffset and actorOffset; value '-1' means ignore all items).

Regards,

--
Jesús García Crespo

[ramcor...@gmail.com]

Que tal Jesus tengo el mismo error intente bajar el parche pero me da pagina no exite si me pueedes enviar a mi correo (ramcor...@gmail.com) o la ueva direccio  donde esta el parche te agradeceria mucho.

Muchas gracias

Saludos

[Dan Gillean]

Hello Ramiro, 

If you are running ICA-AtoM 1.2.1 or higher, then you should not need this patch - it was added to the 1.2.1 release. You can see the details here: 

• https://projects.artefactual.com/issues/3078#note-15
  

Unfortunately, since this patch is now 7 years old, we no longer have a copy of it in any case. 

Is the issue that you want to publish many descriptions as described in the original post, or that you are encountering the segmentation fault error?

If you are trying to publish descriptions, please follow the instructions in the beginning of this thread. If you are encountering the segmentation fault error, you might try doing what Paul did, and locating the empty records in the q_information_object_i18n table of your MySQL database. 

If you are not familiar with SQL queries, I would recommend installing a tool such as PHPMyAdmin, which will give you a user interface through which you can access the database directly.  

Good luck! 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/4c381715-9b37-45b4-945e-81f7d83830f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.