[MediaWiki-l] indexing an existing file store with Mediawiki

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[MediaWiki-l] indexing an existing file store with Mediawiki

rkevans
Hi Folks,

Can you guys help me determine if the following idea is possible with Mediawiki.

Givens --
1. Read-only access to a pre-existing file repository on the server with a well-defined folder structure.
2. The file repository is frozen. No new files or folders are being added to this remote repository.
3. The folder structure is an important part of how users are used to finding what they are looking for.

Problem -- There is a need to allow users to discuss these files and annotate them with updated information about the use, context, accuracy, and relevancy of the files .. and in some cases, where there should be referred to instead.

Desired Solution -- Implement a web-based application that "indexes" the files in their existing file structure and provides a collaborative framework for users to generate supplemental information regarding the use, context, accuracy, and relevancy of the files .. and where they should be referred to instead.

The Result --- The original file store is untouched and we have a wiki where every file in the remote store has been indexed by mediawiki and is searchable by name and the mediawiki users can begin build wiki articles in the usual way referencing the files as articles in the file namespace.

My first question to all of you here is --- Is this possible with Mediawiki?

And, if so, my second question is:

Would the following approach be right?
1. Install a fresh copy of mediawiki (latest) onto a new web-server
2. Disable file uploads from the wiki
3. configure the wiki to see the existing file repository as the image folder  (something like: $wgUploadPath = "<path to remote file store>";
4. run a maintenance script that (re)builds the mediawiki file list from the current files of the remote file repository but does not import actual files.
5. (ideally adds a link the image path as the text of the file article.)

That's my hope.
What are the challenges in using Mediawiki for this type of application?
Are there any extensions that anyone knows of that have this kind of application in mind?
Has anyone attempted this with any level of success?

Thank you!
-Rich

_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Reply | Threaded
Open this post in threaded view
|

Re: indexing an existing file store with Mediawiki

Brian Wolff
On Wed, Apr 4, 2018 at 2:42 PM, Evans, Richard K. (GRC-H000)
<[hidden email]> wrote:

> Hi Folks,
>
> Can you guys help me determine if the following idea is possible with Mediawiki.
>
> Givens --
> 1. Read-only access to a pre-existing file repository on the server with a well-defined folder structure.
> 2. The file repository is frozen. No new files or folders are being added to this remote repository.
> 3. The folder structure is an important part of how users are used to finding what they are looking for.
>
> Problem -- There is a need to allow users to discuss these files and annotate them with updated information about the use, context, accuracy, and relevancy of the files .. and in some cases, where there should be referred to instead.
>
> Desired Solution -- Implement a web-based application that "indexes" the files in their existing file structure and provides a collaborative framework for users to generate supplemental information regarding the use, context, accuracy, and relevancy of the files .. and where they should be referred to instead.
>
> The Result --- The original file store is untouched and we have a wiki where every file in the remote store has been indexed by mediawiki and is searchable by name and the mediawiki users can begin build wiki articles in the usual way referencing the files as articles in the file namespace.
>
> My first question to all of you here is --- Is this possible with Mediawiki?
>
> And, if so, my second question is:
>
> Would the following approach be right?
> 1. Install a fresh copy of mediawiki (latest) onto a new web-server
> 2. Disable file uploads from the wiki
> 3. configure the wiki to see the existing file repository as the image folder  (something like: $wgUploadPath = "<path to remote file store>";
> 4. run a maintenance script that (re)builds the mediawiki file list from the current files of the remote file repository but does not import actual files.
> 5. (ideally adds a link the image path as the text of the file article.)
>
> That's my hope.
> What are the challenges in using Mediawiki for this type of application?
> Are there any extensions that anyone knows of that have this kind of application in mind?
> Has anyone attempted this with any level of success?
>
> Thank you!
> -Rich
>
> _______________________________________________
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

I think you would need a custom (foreign?) FileRepo [1] if you don't
want to have the files copied over to a different directory (like
importImages.php would do).


-
Brian

[1] https://doc.wikimedia.org/mediawiki-core/master/php/classFileRepo.html
https://doc.wikimedia.org/mediawiki-core/master/php/classForeignAPIRepo.html

_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l