Ok, so I did not see that lcnaf was included in ArchivesSpace right from the beginning. I thought I had to get the files from GitHub as I would with other plugins, but I see that they are there. In fact several are there.
So I need to revise my overall question to: - Why is some code added to the zip file but left as a plugin while other code is added to the software? In this instance, lcnaf is there but I need to update the config file to turn it on. With other plugins, I have to get the files from somewhere else and turn them on. And maybe do more than just put them in the directory (for instance, oauth needs to be compiled). How is it determined what goes where and how it is or is not included? Sorry, but this is rather confusing to the newbie. Thanks Tom On Thu, May 20, 2021 at 10:51 AM Joshua D. Shaw <joshua.d.s...@dartmouth.edu> wrote: > Hi Tom > > To enable any plugin in the /plugins directory, you need to update the > config file. Specifically, the entry > > AppConfig[:plugins] = [] > > The array contents are just the directory names of the plugins that you > want to enable > > So, to enable just the lcnaf plugin, you would want > > AppConfig[:plugins] = ['lcnaf'] > > https://archivesspace.github.io/tech-docs/ is a good resource. > > jds > > ------------------------------ > *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < > archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Tom > Hanstra <hans...@nd.edu> > *Sent:* Thursday, May 20, 2021 9:09 AM > *To:* Archivesspace Users Group < > archivesspace_users_group@lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] lcnaf plugin > > Hi, ArchivesSpace users, > > I continue my quest to get our site set up and have been told that I need > to install the lcnaf plugin. I've got a few questions: > > First, where is the documentation on how to install the plugin? The code > in github does not have so much as a README file to give me information on > how to install it. Do I just grab the code and plunk it into the plugins > directory? Or is there more to be done? > > Second, how does ArchivesSpace decide what plugins get pulled into code > and which do not. This one, from what I can tell, has been around for a > long time and yet continues to be a plugin that is added after the fact. > Yet other plugins have been added into the code. Just curious how that gets > decided. > > Thanks, > Tom > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hans...@nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hans...@nd.edu
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
